tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 21219] - Corrupted Message Body on interrupted GET
Date Fri, 04 Jul 2003 11:50:50 GMT
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=21219>.
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=21219

Corrupted Message Body on interrupted GET





------- Additional Comments From remm@apache.org  2003-07-04 11:50 -------
Apache closes the connection on a 404 ?
If the answer is always yes, then -0 for your patch (so I'm not vetoing, but I'm
very close to that), otherwise, -1. I don't think we should always attempt to
match the HTTPd behavior when we can do something which matches the spec and is
more powerful. At least add a flag on the connector to allow configuring this
(just like there's a flag to disconnect after a certain amount of requests).

If the response has already been committed, I think your patch is ineffective,
so is why I think it is a bad idea overall. There's also the fact that you're
closing the connection without adding a Connection: close header (it's ok not
to, but still ...).

As I said in a previous comment, the only error we should detect in the HTTP
layer is if the amount of data written doesn't match the content length. Right
now, it is an error when less bytes are written, but if more are written, bytes
are swallowed and the error flag is not set (which of course, is not a protocol
violation).

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org


Mime
View raw message