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 header field in the request's message-headers. </quote> Unfortunately there are tons of web servers out there that simply do not give a damn. The code in CVS has already been to not log the warning if the target server sends 'connection: close' directive along. HttpClient 2.0rc3, once released, should not exhibit this problem anymore. Oleg -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, November 21, 2003 15:20 To: [EMAIL PROTECTED] Subject: Thounds of "Response content length is not known" in the log file 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 think he is not, isn't he? I switched back to RC1 and do not get any log entries of this type. But what I think, is: if existence of header content-length is not mandatory there should only be created a log entry with log level TRACE instead of WARN, shouldn't it? Thanks, Klaus Kopruch ---------------------------- MATERNA GmbH Klaus Kopruch Vosskuhle 37 44141 Dortmund GERMANY Phone: +49 231 5599-8947 Fax: +49 231 5599-67 8947 +49 231 5599-350 Mobil: +49 173 70 78 207 Web: http://www.annyway.de <http://www.annyway.de/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
