On Thu, 2008-01-24 at 17:11 -0500, John Wehle wrote:
> Currently if a servlet uses:
>
> res.setHeader("Connection", "close");
>
> tomcat just sets the header and sends the reponse to the client. It
> then waits for the client to close the connection. In some cases (i.e.
> buggy client) the client doesn't process the close which causes resources
> to be unduly tied up on the server until the connectionTimeout is reached
> which then closes the connection. This also causes the user to experience
> a browser delay corresponding to connectionTimeout.
>
> This patches causes tomcat to close a connection after sending a response
> which includes "Connection: close".
The rationale is that a servlet has no business dealing with the
connection behavior: if the client has problems, you can add appropriate
configuration in the connector.
Rémy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
