[
https://issues.apache.org/jira/browse/TS-4328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15318805#comment-15318805
]
ASF subversion and git services commented on TS-4328:
-----------------------------------------------------
Commit f15396674429853dc7f5bcac15cb1b4d671ebb39 in trafficserver's branch
refs/heads/6.2.x from [~jacksontj]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=f153966 ]
TS-4328 Not retry if any bytes were sent
Before we would still retry if the origin didn't error-- but just took a really
long time. So, instead of only checking if the body was sent-- we can check the
SM to see if we wrote any header bytes to the wire. If any bytes were sent the
request cannot be retried.
This closes #554
This also deprecates the `request_body_start` field, and as such removes it
(cherry picked from commit f129996e1adaab399359cd248f4750a686d6bfc5)
Conflicts:
proxy/http/HttpTransact.h
> Connect_retries re-connects even if request made it to origin (TS-3440 repeat)
> ------------------------------------------------------------------------------
>
> Key: TS-4328
> URL: https://issues.apache.org/jira/browse/TS-4328
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Thomas Jackson
> Assignee: Thomas Jackson
> Fix For: 6.2.0, 7.0.0
>
>
> I'm creating another issue as the root bug for TS-3440 can still be
> reproduced if the origin is extremely slow (but no returns no error response).
> I've opened a PR (https://github.com/apache/trafficserver/pull/554) which
> reverts the original patch and instead checks if any bytes where sent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
