Alfonso, Nightly builds that you are using contain experimental and unstable code. 2.1 branch is in a state of profound flux. We are still trying to finalise the API and simply have no bandwidth to deal with the bugs in the experimental code. Please retest your application using the latest official release (2.0rc2 as of writing) and if the problem persists please submit the <strong>complete</strong> wire log. I'll happily take look and try to come up with a solution.
> >> The cause of the problem is that HttpMethodDirector expects not to > >> see a response body until the authentication process is finished, > >> that is, it understands that things should be ok the moment a > >> response body is present. This assumption is not correct. HttpClient never 'ignores' (or should never ignore) a response body. HttpClient may discard one when it handles certain type of responses automatically (for instance, redirects or authentication challenges) > >> HttpMethodBase#canHaveResponseBody. As I understand that method is > >> provided to ignore response bodies for certain return codes. That is, > >> around line 2126 it says Not entirely correct. HttpClient relies on this method to force-close the connection if it receives content body for a response type for which content body is not allowed. 407 clearly does not fall into such a category. It already happened more than once or twice here that people reported what they thought was a bug in Httpclient, when in fact the problem were caused by their use of invalid credentials. Oleg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
