It would appear that setting the Credentials property of a HttpWebRequest still leads to authentication failure against the Superfeedr HTTP PubSubHubbub API. This might be because the way the HttpWebRequest works is that it first waits to be challenged for credentials via a 401 (not authorized) and then replies with the authentication (more info include PreAuthenticate here).
So, this doesn’t work:
string username = "username";
string password = "password";
HttpWebRequest request = (HttpWebRequest)WebRequest.Create("url-here");
request.Credentials = new NetworkCredential(username, password);
To work around this you need to force the authentication to be sent. I found the details of how to do this in a blog post by Ian Dykes here:
http://devproj20.blogspot.com/2008/02/assigning-basic-authorization-http.html
But for fullness here’s the code:
string username = "username"; string password = "password"; byte[] authBytes = Encoding.UTF8.GetBytes(username + ":" + password.ToCharArray()); request.Headers["Authorization"] = "Basic " + Convert.ToBase64String(authBytes);
With my interest in Comet I straight away thought of this as a solution to the notification requirement and it’s interesting that the article goes on to talk about subscription management and then moves on to thinking about the delivery mechanism which are all key aspects of a good comet implementation: