[
https://issues.apache.org/jira/browse/TS-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072669#comment-13072669
]
William Bardwell commented on TS-749:
-------------------------------------
The problem is that the content might not be the same the next time you ask
(for a range request), so inconsistent content could be served up, although
sometimes you could tell either way based on ETag or Last-Modified-Time, but
not always. The more basic issue is that ATS doesn't handle partial content in
the cache yet, although that would be great to have it be fixed, then fixing
this in some cases, or when enabled by config, would be feasible.
> 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
