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 7852] - Closing connections on error causes problems
Date Mon, 08 Apr 2002 20:52:04 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=7852>.
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=7852

Closing connections on error causes problems

remm@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From remm@apache.org  2002-04-08 20:52 -------
Closing the connection for whatever reason is always valid in HTTP/1.1, esp 
when announcing that you'll be doing so. For example, some HTTP/1.1 always add 
the connection: close header in the response.
So it does not violate any intent, and is perfectly legal.

You should never rely on the connection being persisted for any operation (or 
this makes your client app non-HTTP compliant).

If you hack the code there, it WILL create problems, and make Tomcat generate 
non-compliant HTTP responses (yes, the code is there for a reason).

Coyote does not suffer from the limitations of the old HTTP connector, and is 
able to always persist the connection.

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


Mime
View raw message