Oleg,

Dang, you're good! You complete fixes before others can even guess at them!

-Eric.

Oleg Kalnichevski wrote:

It strikes me personally that the "warning" in this particular context is probably excessive, and it should be logged as a "info" or "debug" message instead, but only in this particular case. If you look at the wire log you'll notice that the server does not respond with a "Content-Length" header. Rather, the length of the response is dictated by when the server closes the connection to the client. HttpClient is telling the truth with this warning that you see, but in this particular context, the server explicitly indicates that it will be closing the connection.



Eric, you are completely right. I realised that a few days ago and already applied a fix for the problem. The most recent 2.0 code snapshot will not display the warning when content length cannot be determined but 'connection: close' directive is given.

Oleg


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to