You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Conan Wang (JIRA)" <ji...@apache.org> on 2011/07/28 12:32:10 UTC

[jira] [Commented] (TS-749) Connection hangs if origin server goes down in the middle of a response

    [ https://issues.apache.org/jira/browse/TS-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13072290#comment-13072290 ] 

Conan Wang commented on TS-749:
-------------------------------

If origin server goes down or there is some network issue when transferring object (after connected), can ATS retry to fetch the object again?  After several times, if OS really goes down, then ATS should log it to error_log.

> 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