You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2015/03/13 03:36:38 UTC
[jira] [Commented] (TS-3440) Connect_retries re-connects even if
request made it to origin
[ https://issues.apache.org/jira/browse/TS-3440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14359823#comment-14359823 ]
ASF GitHub Bot commented on TS-3440:
------------------------------------
GitHub user jacksontj opened a pull request:
https://github.com/apache/trafficserver/pull/179
Tests for TS-3440 and TS-3439
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacksontj/trafficserver master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/trafficserver/pull/179.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #179
----
commit 28059ccb93f9fb173792aeebf90062882dfdf9d5
Author: Thomas Jackson <ja...@apache.org>
Date: 2015-03-13T02:06:05Z
Add tests for connect_attempts within (retries for connection to origin)
commit e221e91ad6466ef840f74a1016b8d51c821eb1e9
Author: Thomas Jackson <ja...@apache.org>
Date: 2015-03-13T02:28:26Z
Add initial chunked encoding tests
----
> 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
>
> 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).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)