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

["Alan M. Carroll (JIRA)" <ji...@apache.org>]

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

Alan M. Carroll commented on TS-242:
------------------------------------

I think a good intermediate step would be create a milestone for server connect. [~zwoop] and I tested this and we can detect the socket level connect by detecting the socket becoming writable. If we have a milestone for that event, that would be useful of itself and make it relatively easy to do this as well. In addition having the milestone would simplify debugging whether this was working (as testing timeouts can be difficult).

> 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
>            Assignee: Leif Hedstrom
>            Priority: Minor
>             Fix For: 7.0.0
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)