https://bz.apache.org/bugzilla/show_bug.cgi?id=65201
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Mark Thomas <ma...@apache.org> ---
If an application sets "Transfer-Encoding: chunked" then the application also
has to take responsibility for generating the appropriate chunk headers. This
is non-trivial.
It is much better to let containers handle this for the application.
Applications that try to do this themselves will quickly hit all sorts of
complications and edge cases. Applications also need to check they aren't
running over HTTP/1.0 or HTTP/2 since chunked is not supported.
In this case, setting the headers (less "Transfer-Encoding" and "Connection")
and flushing the (currently empty) response will do the right thing for all
HTTP versions.
There has been some discussion about blocking applications from setting certain
headers. Transfer-Encoding and Connection were both included in that
discussion. However, the discussion concluded that a better approach would be
to implement the equivalent of mod_headers for Tomcat.
Resolving as invalid since this is an application bug.
--
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
