Wait a sec ... not enough coffee. I might have answered a totally
different question (and incorrectly too)
-Tim
On 4/1/2010 6:42 AM, Tim Funk wrote:
Doing this would be bad. When serving JSP's (or anything dynamic greater
than the buffer size) - the content length is not sent to the client. So
when the end of the request is sent - there is no signal to the client
to let them know the request is over and they can start a new request
over the same connection.
With chunked encoded - we can get away with no content length header
because the each chunk as the length.
-Tim
On 4/1/2010 6:02 AM, Óscar Frías Barranco wrote:
Hello.
Currently Tomcat HTTP 1.1 Connector disables the use of chunked
encoding if
keepalive is not used. This happens when an HTTP 1.1 request contains a
"Connection: close" header.
I propose to change Coyote to use chunked encoding (for HTTP 1.1) even if
keepalive is disabled.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
