tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 50494] Need to add ability to disable chunked encoding or support HTTP 1.0 response.
Date Tue, 04 Jan 2011 15:16:38 GMT changed:

           What    |Removed                     |Added
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |
           Severity|critical                    |enhancement

--- Comment #4 from 2011-01-04 10:16:35 EST ---
Given how fast you reject enhancement requests, I feel it will be waste of
time, but, just to please you I am making the changes:

I use NIO HTTP Tomcat connector org.apache.coyote.Http11NioProtocol to
implement Comet streaming to browsers and mobile devices. 
The application opens 'primary' persistent Comet connection to receive data
from the server. Server sends data to the client periodically.

Currently, the response always uses HTTP 1.1 type response with chunked

There could be a legitimate reason to disable chunked encoding - use
"Connection: close" without "Content-Length" headers.

For example, if I use tomcat to implement EventType streaming with Chrome, it
does not like chunked encoding and fails to receive any data. Also, chunked
encoding increases network bandwidth.

One way to disable chunked encoding (and actually the one I would prefer) is to
force HTTP 1.0 response.

1) force HTTP 1.0 response.
2) use HTTP 1.1 response, but disable chunked encoding.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message