[
https://issues.apache.org/jira/browse/TS-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072662#comment-13072662
]
Conan Wang commented on TS-749:
-------------------------------
In a cache miss transaction, the object is simultaneously streamed to UA and
ATS local cache. In the midway of streaming (especially for large object), if
there is an abort between ATS and OS, I think ATS should not abort the
connection to UA immediately, and ATS could re-issue RANGE request to OS(or
RoundRobin backup OS) for the rest content of the object at an acceptable retry
times/timeout, in order to continue the streaming.
> Connection hangs if origin server goes down in the middle of a response
> -----------------------------------------------------------------------
>
> Key: TS-749
> URL: https://issues.apache.org/jira/browse/TS-749
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Affects Versions: 2.1.7, 2.1.6, 2.1.5, 2.1.4
> Environment: Any
> Reporter: William Bardwell
> Assignee: Leif Hedstrom
> Fix For: 2.1.8
>
> Attachments: svn.diff
>
>
> If you start a long HTTP response, and then kill the origin web server, the
> connection to the client goes idle. It looks like TS would accept further
> commands, but the client doesn't know that the response is finished. After a
> few minutes an idle timeout will close the connection. Instead the
> connection should be closed, allowing the client to notice that it only got a
> partial response in some cases, and letting it proceed in all cases.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
