[
https://issues.apache.org/jira/browse/TS-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14605118#comment-14605118
]
Brian Geffon commented on TS-3440:
----------------------------------
[~jacksontj] looking at your tests you're assuming that we should send back a
504 to the client; however, I'm not sure this is actually an option simply
because we may have begun sending the headers to the client. ATS can send the
client response headers as soon as it receives them from the origin so if the
client response headers have been sent you definitely can't always assume a
504. I do agree though that we _should not_ reestablish the connection and send
another request.
> Connect_retries re-connects even if request made it to origin
> -------------------------------------------------------------
>
> Key: TS-3440
> URL: https://issues.apache.org/jira/browse/TS-3440
> Project: Traffic Server
> Issue Type: Bug
> Reporter: Thomas Jackson
> Assignee: Brian Geffon
> Fix For: sometime
>
>
> While trying to workaround TS-3439 I decided to test out the connect retries
> option. During testing I found a case where it should not retry where it is.
> The scenario is as follows:
> - ATS makes a connection to an origin
> - the origin acks the entire request
> - the origin starts to send back a response (lets say first line of the
> header)
> - the origin sends an RST
> In this scenario ATS will re-connect to the origin, which is bad since we
> have already sent the request (and we aren't sure if the URL is re-entrant).
> Test case:
> https://github.com/jacksontj/trafficserver/commit/28059ccb93f9fb173792aeebf90062882dfdf9d5#diff-06f9ddbe6cc45d76ebb2cb21479dc805R182
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
