You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2016/10/03 19:17:21 UTC

[jira] [Commented] (TS-4921) Safe HTTP methods should be retryable.

    [ https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543165#comment-15543165 ] 

Leif Hedstrom commented on TS-4921:
-----------------------------------

I assume this is worked on now, so setting version to 7.1.0. Move out to "sometime" if that's not the case.

> Safe HTTP methods should be retryable.
> --------------------------------------
>
>                 Key: TS-4921
>                 URL: https://issues.apache.org/jira/browse/TS-4921
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core, HTTP
>            Reporter: James Peach
>            Assignee: Thomas Jackson
>             Fix For: 7.1.0
>
>
> In {{HttpTransact::is_request_retryable}}, nothing seems to be retryable if you have sent any bytes. Following the RFCs, the default behaviour should allow safe (and also idempotent) method requests to be retried regardless of thether bytes were sent.
> "safe" methods (https://tools.ietf.org/html/rfc7231#section-4.2.1): GET HEAD
> From conversations, it sounds like the ideal approach is to create a config option (which is transaction overrideable) which allows you to define the list of methods which are retryable (which wouldn't be limited to the well-known methods inside ATS).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)