https://issues.apache.org/bugzilla/show_bug.cgi?id=50494
Mark Thomas <ma...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
--- Comment #5 from Mark Thomas <ma...@apache.org> 2011-01-04 10:52:52 EST ---
Tomcat aims to implement the various specifications (HTTP, Servlet, etc.) as
closely as possible and deviates from those specifications only when there is a
very good reason to do so. Working around bugs in third party applications is
typically not viewed as good reason to diverge from the specifications.
Quoting from section 4.4 of the HTTP 1.1 spec:
<quote>
All HTTP/1.1 applications that receive entities MUST accept the
"chunked" transfer-coding (section 3.6), thus allowing this mechanism
to be used for messages when the message length cannot be determined
in advance.
</quote>
With the above in mind, this looks like a bug in the user agent.
I can think of several ways to force a non-chunked response with the current
Tomcat versions. As I said previously, the users mailing list is the place to
discuss this. If a discussion on the users list identifies a use case that
isn't currently supported, that would be the point to re-open this issue.
--
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
