[
https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14309487#comment-14309487
]
ASF subversion and git services commented on TS-242:
----------------------------------------------------
Commit d77730387c41359cd3612fd4462865bbfe0ac57d in trafficserver's branch
refs/heads/master from [~dcarlin]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=d777303 ]
Clarify Origin Server Connect Attempts documentation
TS-242: make it clear that proxy.config.http.connect_attempts_timeout is
for time to first byte
> 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)
