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

Thomas Jackson updated TS-4921:
-------------------------------
    Description: 
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).


  was:
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: 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).



> 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
>
> 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)

Reply via email to