https://issues.apache.org/bugzilla/show_bug.cgi?id=50275
Tim Whittington <t...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
--- Comment #1 from Tim Whittington <t...@apache.org> 2010-11-17 03:13:35 EST
---
This doesn't sound like a Tomcat bug:
- The AJP connector in Tomcat (on the Java side) does not do chunked encoding -
this is done by the web server (in the case of Apache - i.e. not mod_jk) or the
ISAPI Redirector (in the case of IIS).
- If you're setting Transfer-Encoding: chunked in a servlet, then everything
else in the response chain back to the browser will assume that you're also
chunk encoding the response body, otherwise how would Tomcat know whether you'd
chunk encoded the body or it had to?
For comparison the DefaultServlet in Tomcat does HTTP byte range responses
(which have similar implications for response encoding and message length
detection to chunked encoding) and Tomcat and mod_jk behave well with that.
There's also the question of why you'd want to explicitly set
Transfer-Encoding: chunked on a response when every available connector
exposing your content to the client supports it already without you having to
do anything...
If I'm misunderstanding the situation, please attach a sample servlet and
mod_jk DEBUG + HTTP trace that illustrates the problem.
--
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
