https://issues.apache.org/bugzilla/show_bug.cgi?id=50494
gober...@msn.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |
Severity|critical |enhancement
--- Comment #4 from gober...@msn.com 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
encoding.
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.
PLEASE ADD AN OPTION TO:
1) force HTTP 1.0 response.
2) use HTTP 1.1 response, but disable chunked encoding.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
