You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/06/24 07:45:00 UTC

[jira] Updated: (TS-242) Connect timeout doesn't reset until first byte is received from server

     [ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-242:
-----------------------------

    Fix Version/s: 2.1.2

> Connect timeout doesn't reset until first byte is received from server
> ----------------------------------------------------------------------
>
>                 Key: TS-242
>                 URL: https://issues.apache.org/jira/browse/TS-242
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>            Reporter: Steve Jiang
>            Priority: Minor
>             Fix For: 2.1.2
>
>
> proxy.config.http.connect_attempts_timeout
> proxy.config.http.parent_proxy.connect_attempts_timeout
> proxy.config.http.post_connect_attempts_timeout
> These timeouts are implemented with inactivity timeout on the netvc and don't behave as expected.  
> If the connect succeeds (the remote server successfully accepted) but the remote server does not respond with any bytes within the timeout period, TS still treats it as a connect timeout.  If retries are enabled and the origin server is slow to start sending responses (but not down), it will keep sending requests and closing the connection after getting no response within the connect timeout.

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