Hi Roland, Yeah, that's what I thought. I raised the issue with the Jetty developers but it sounds like the behaviour is embedded fairly deeply in the architecture.
Guess I'll have to live with. Thanks for the suggestions though. Regards Tony -----Original Message----- From: Roland Weber [mailto:[EMAIL PROTECTED] Sent: 10 June 2005 15:28 To: HttpClient User Discussion Subject: RE: Unbuffered entity enclosing request can not be repeated Hello Tony, > DEBUG [httpclient.wire.header] << "HTTP/1.1 100 Continue[\r][\n]" > DEBUG [com.cibecs.brs.core.net.http.RequestMethod] **** writeRequestBody() > DEBUG [httpclient.wire.header] << "HTTP/1.1 401 Unauthorized[\r][\n]" > DEBUG [httpclient.wire.header] << "Date: Fri, 10 Jun 2005 06:26:07 > GMT[\r][\n]" > DEBUG [httpclient.wire.header] << "Server: Jetty/5.1.3rc3 (Windows XP/5.1 > x86 java/1.5.0_02[\r][\n]" > DEBUG [httpclient.wire.header] << "WWW-Authenticate: basic > realm="agent"[\r][\n]" > DEBUG [httpclient.wire.header] << "Content-Type: text/html[\r][\n]" > > Hmmm ... the server is returning a '100 Continue' followed immediately by a > '401 Unauthorized'. Is that correct ? It certainly isn't what the server is supposed to do. Sending a 100-continue reply even though authentication is required beats the whole purpose of the handshake. Maybe the Jetty guys know more about this? cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
