[
https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14253676#comment-14253676
]
Leif Hedstrom commented on TS-242:
----------------------------------
We just ran into this issue, and it caused some major headache, and of course,
confusion. We really ought to switch the timeout from e.g.
proxy.config.http.connect_attempts_timeout to
proxy.config.http.transaction_no_activity_timeout_out after the connection has
been successfully accepted by the other side. There's probably a few places
where this happens, and we'd want to make sure to use the appropriate _out
timeout.
> 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: Alan M. Carroll
> Priority: Minor
> Fix For: 5.3.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)
