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 [EMAIL PROTECTED] 2003-07-01 19:07 ------- Well, you have a few options to play with: - try to catch the runtime exception; it it happens that often, you should handle it better - extend the error report valve to suit your needs better - don't set content-length (it doesn't improve performance on the server side, as Coyote's chunking is extremely efficient) Coyote considers that if less bytes are written, then there's a protocol error (obviously). If too many bytes are written, the remaining bytes are eaten, but there's no protocol error; maybe the error flag could be set in that cases (in which case the connection would be closed at the end of the request processing). --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
