[jira] [Closed] (TS-3440) Connect_retries re-connects even if request made it to origin

["Thomas Jackson (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Thomas Jackson closed TS-3440.
------------------------------
    Resolution: Duplicate

Re-closing-- as [~zwoop] prefers a separate ticket (for changelog etc).

new ticket: https://issues.apache.org/jira/browse/TS-4328

> 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: Thomas Jackson
>
> 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)