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=10541>. 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=10541 Content-length header should be automatically set for buffered Servlets/JSPs [EMAIL PROTECTED] changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | ------- Additional Comments From [EMAIL PROTECTED] 2002-10-17 22:12 ------- I'll reopen the bug, since I also seem to have an itch with it. The major problem is that it's hard to know ( from connector side ) when you have this case, and the END will follow imediately after the first chunk. The only way to detect it is higher - and distinguish between a SEND that happens normally and the SEND+END that happens when the JSP/servlet finishes the request and the container is automatically flushing the buffer. I don't see any other solution, at least at container level - you can't guess that END will follow. The problem is finding the exact point where the flushing happens. Remy - if you want to close this, please mark it as REMIND or LATER, I'll fix it ( if I figure out how :-) -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
