DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24869.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24869.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24869.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
Hi,
up to now I used RC1 without problems. After switching to RC2 I get
thousands of log entries Response content length is not known (WARNING).
This log entry seems to be created because the server does not send the http
header content-length within the response. But is he obliged to do so? I
Klaus,
RFC 2616 mandates the presence of either 'Content-Length' or 'Transfer-Encoding' if
the target server is going to return a content body:
quote
4.3 Message Body
...
The presence of a message-body in a request is signaled by the
inclusion of a Content-Length or Transfer-Encoding
Oleg,
Do you remember why this ugly code was introduced?
if (canResponseHaveBody(statusLine.getStatusCode())) {
Header connectionHeader =
responseHeaders.getFirstHeader(Connection);
String connectionDirective = null;
if
oh I see that transfer encoding is taken care of. So ignore the passage
about that in my previous posting. Still we should engange
shouldCloseConnection here because of the difference in HTTP/1.0 and 1.1
-
To unsubscribe,
Odi,
In this case I personally think that a warning message is quite appropriate.
Oleg
-Original Message-
From: Ortwin Glück [mailto:[EMAIL PROTECTED]
Sent: Friday, November 21, 2003 16:11
To: Commons HttpClient Project
Subject: Re: Thounds of Response content length is not known in the
True.
Klaus, could you provide a wire log that shows the server's response
leading to such a warning? I would just like to check if the warning is
issued correctly. Cheers.
Odi
Kalnichevski, Oleg wrote:
Odi,
In this case I personally think that a warning message is quite appropriate.
Oleg
But not thousands :-(
May be it should be possible to configure bad servers which are allowed
to respond without content-length.
-Ursprüngliche Nachricht-
Von: Kalnichevski, Oleg [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 21. November 2003 16:14
An: Commons HttpClient Project
Yes, of course!
I'll do it on monday.
Klaus.
-Ursprüngliche Nachricht-
Von: Ortwin Glück [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 21. November 2003 16:28
An: Commons HttpClient Project
Betreff: Re: Thounds of Response content length is not known in the
log file
True.
Not a thousand. Just one per request.
As I said already, if the server in question does not do something outrageously stupid
(like sending neither 'Content-Length' nor 'Transfer-Encoding', nor 'Connection:
close') the problem has already been solved for rc3
Oleg
-Original Message-
Hi
I'm new to HttpClient and I was hoping someone could help use the NTLM authentication
correctly. I have
the neccassary permissions because I can get to the site through Internet Explorer
without any problem.
After seeing some discussion of problems with with NTLM in -rc1 I've upgraded to
Try this code:
SimpleHttpConnectionManager theConnectionManager = new
SimpleHttpConnectionManager();
HttpClient theClient = new HttpClient( theConnectionManager );
//Set The Proxy Host Configuration
HostConfiguration theHostConfiguration = theClient.getHostConfiguration();
Hi Khalid
Thanks for the prompt response. Your code produces the follwoing message;
INFO: Already tried to authenticate with 'null' authentication realm at
www-proxy2.uk.int.atosorigin.com, but still receiving: HTTP/1.1 407 Proxy
Authentication Required ( The ISA Server requires authorization
Varley, Roger wrote:
Hi Khalid
Thanks for the prompt response. Your code produces the follwoing message;
INFO: Already tried to authenticate with 'null' authentication realm at www-proxy2.uk.int.atosorigin.com, but still receiving: HTTP/1.1 407 Proxy Authentication Required ( The ISA Server
16 matches
Mail list logo