Mailing-List: contact issues-help@trafficserver.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@trafficserver.apache.org
Message-ID: <12414301.81631289249529912.JavaMail.jira@thor>
Date: Mon, 8 Nov 2010 15:52:09 -0500 (EST)
From: "Leif Hedstrom (JIRA)" <jira@apache.org>
To: issues@trafficserver.apache.org
Subject: [jira] Created: (TS-518) Close UA connection early if the origin
 sent Connection close:, there's a bad Content-Length header, and the UA
 connection has Keep-Alive.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Close UA connection early if the origin sent Connection close:, there's a bad Content-Length header, and the UA connection has Keep-Alive.
------------------------------------------------------------------------------------------------------------------------------------------

                 Key: TS-518
                 URL: https://issues.apache.org/jira/browse/TS-518
             Project: Traffic Server
          Issue Type: Bug
          Components: HTTP
            Reporter: Leif Hedstrom
             Fix For: 2.1.5


In a very special case, we could improve the user experience by forcefully closing the connection early. The case is

1) The origin server sends a Content-Length: header that is wrong, where the CL: value exceeds the actually body size.

2) The origin server either sends a Connection: close, or it uses HTTP/1.0 without keep-alive.

3) The client (and TS) uses Keep-Alive to the UA.


In this case, we can end up stalling the UA until either the UA or the TS connection times out. It might make sense to prematurely disconnect the client when this case is detected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.