|
I'm trying to use the API to validate DynDNS credentials, and the documentation says that the 'badauth' response is meant for exactly that. Great! With that I can automate an update with some credentials and look for the badauth response and use that to detect incorrect credentials, sounds perfect.
Any idea what I'm missing here? |
|
Solution found!
Even though WebRequest.Create accepts a Uri instance and Uri understands embedded credentials, HttpWebRequest.GetResponse obviously doesn't treat these two methods of specifying credentials equivalently because one works and the other doesn't. |
|
I could imagine that you're locked out for a while if you attempted too many invalid authentications. You may have to wait several cups of coffee before it will work again with valid credentials. I would imagine that if that were the problem I'd be getting the 'abuse' response instead of the 'badauth' response. It's definitely a 401 Unauthorized exception being thrown with 'badauth' in the response body.
Dec 05 at 07:21 PM
Task
|