DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8470>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8470
missing content-length from the header, Apache/Tomcat/AJP12 Connector spins out of control
william.barker@wilshire.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From william.barker@wilshire.com 2002-04-29 02:02 -------
Under the HTTP/1.1 RFC, sending the content-length is optional. The browser
may choose to send it with chunked-encoding. This is probably what you are
seeing.
If you upgrade to 3.3.1, then the AJP12Connector won't die (with smarter, but
similar, logic than below). If you also upgrade to the AJP13Connector, then
Tomcat will be able to handle the case of chunked-encoding.
Marking as WONTFIX, since the 3.2.x line is no longer under active development,
and the AJP12Connector is deprecated in 3.3.x.
--
To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:tomcat-dev-help@jakarta.apache.org>
|