W3C home > Mailing lists > Public > www-talk@w3.org > September to October 2003

Re: HTTP/1.1 Chunked Transfer Encoding

From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
Date: 24 Oct 2003 10:56:15 +0100
To: michael_pacey@standardlife.com
Cc: www-talk@w3.org
Message-ID: <87u15zgds0.fsf@kanga.tapsellferrier.co.uk>

michael_pacey@standardlife.com writes:

> Hi,
> 
>  Apologies if this isn't the right list.
> 
> A simple question regarding chunked transfer encoding.
> 
> We have a J2EE server which exhibits the following behaviour. A J2EE
> application sends an XML message in response to a POST request. Sometimes
> the response uses chunked transfer encoding. When it does, HTTP headers are
> included in the content of the first chunk, like this:
> 
> HTTP/1.1 100 Continue
> Date: Tue, 21 Oct 2003 09:49:54 GMT
> Server: xxxxxxxxxxx/xxx  Apache/1.3.20 (Unix)
> Transfer-Encoding: chunked
> Content-Type: text/html
> 
> 1000
> HTTP/1.1 200 OK
> Server: xxxxxxxxxxxxxxxxxxx/x.x
> Content-Type: text/xml; charset=ISO-8859-1
> Set-Cookie: JSESSIONID=00002NIZZPVLHKOY1JUST5RFHCA:unv3ultr;Path=/
> Cache-Control: no-cache="set-cookie,set-cookie2"
> Expires: Thu, 01 Dec 1994 16:00:00 GMT
> Content-Length: 5997
> Content-Language: en
> 
> <?xml version="1.0" encoding="ISO-8859-1"
> ?><message><m_control><control_timestamp>

I an't see the rest of your question but I think your J2EE server has
a broken chunked encoding implementation because the first chunk
starts only after the headers have been sent.


Nic Ferrier
Received on Friday, 24 October 2003 05:56:59 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 27 October 2010 18:14:28 GMT