We ran into the same problem (and used the same temporary workaround). It
seems to me that HttpAuthenticator.selectAuthScheme should take into account
the credentials that are available, skipping authentications schemes without
credentials. In your case, since you only provided
UsernamePasswo
, Kalnichevski, Oleg wrote:
> Steve,
> Integrated callbacks are planned for the next release (currently designated
> as 2.1)
>
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10794
>
> Oleg
>
> -Original Message-
> From: Steve Vaughan [mailto:[EMAIL PROTECTED
e the response header
yourself, but this is already being performed by HttpClient.
-Steve
On Tuesday 30 September 2003 08:30 am, Adrian Sutton wrote:
> On 30/09/2003 10:12 PM, "Steve Vaughan" <[EMAIL PROTECTED]> wrote:
> > One of our engineers developed a patch
One of our engineers developed a patch for HttpClient which allows a callback
handler to be registered with an HttpClient instance. A registered handler
could prompt the user for username/password. When a handler isn't
registered, the HttpClient works as it does now.
-Steve
On Monday 29 Sept
When setting the request content length of an enclosed entity to be
stored on the WebDAV server using the PutMethod, the HttpClient returns
an "Unbuffered entity enclosing request can not be repeated"
HttpException. I am aware that if the request is not buffered, then the
PutMethod (or PostMethod)
