DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30273>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=30273

The HTTP 1.1 processor ignores "Connection: close" on response





------- Additional Comments From [EMAIL PROTECTED]  2004-07-22 22:33 -------
There are a lot of other things: transfer encoding, content encoding, etc. I
don't want to start touching these functionality, since there are *way* too many
checks that would have to be done. My opinion in the end is that the servlet
should have as little control as possible on the transport (which makes sense,
since it's non portable); I'm already not too happy about the way a servlet can
flush and end a response (but I think these have a few use cases).

In this bug report, if there is a broken client, you should use a restricted
user-agent parameter rather than hack the servlets.

So definitely WONTFIX.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to