> Otherwise, dynamically generated content would have been a major problem > with HTTP/1.0, or so I figure.
Actually it has been as a problem. That is primarily why HTTP/1.1 had to introduce the generic 'transfer-encoding' mechanism and the chunk encoding as its default implementation. Anyways, you are right. HTTP/1.0 responses that include an entity body may ommit the 'content-lenght' header. I'll provide a patch to disable the warning for HTTP/1.0 responses Oleg -----Original Message----- From: Roland Weber [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 18, 2004 11:46 AM To: Commons HttpClient Project Subject: RE: Response content length is not known Hi Oleg, "Kalnichevski, Oleg" <[EMAIL PROTECTED]> wrote on 18.08.2004 11:26:10: > << "HTTP/1.0 200 OK[\r][\n]" > << "Date: Thu, 19 Aug 2004 02:01:34 GMT[\r][\n]" > << "Server: Oracle9iAS (9.0.3.0.0) Containers for J2EE[\r][\n]" > << "Content-Type: text/html[\r][\n]" > > As you can see the response does not contain a 'content-length' > header which is mandatory for the 200 (OK) response, hence the warning > > <RFC1945> > > 7.2 Entity Body > > ... > > For response messages, ... [a]ll 1xx (informational), 204 (no > content), and 304 (not modified) responses must not include a body. > All other responses must include an entity body or a Content-Length > header field defined with a value of zero (0). > > > </RFC1945> It says "or". Meaning if there is a body, there is no need for the Content-Length header, right? It's mandatory only with value 0, to indicate that there is no body. Otherwise, dynamically generated content would have been a major problem with HTTP/1.0, or so I figure. But I'm not familiar with RFC 1945, so please correct me if I'm wrong. cheers, Roland *************************************************************************************************** The information in this email is confidential and may be legally privileged. Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *************************************************************************************************** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
