[ https://issues.apache.org/jira/browse/TS-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196370#comment-14196370 ]
Alan M. Carroll commented on TS-518: ------------------------------------ Is it presumed the origin server has sent a FIN or RST on the connection? > 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 > Assignee: Susan Hinrichs > Fix For: 5.2.0 > > > 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 was sent by Atlassian JIRA (v6.3.4#6332)