[jira] [Updated] (TS-4921) Safe HTTP methods should be retryable
[
https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Call updated TS-4921:
---
Summary: Safe HTTP methods should be retryable (was: Safe HTTP methods
should be retryable.)
> 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)
[jira] [Updated] (TS-4921) Safe HTTP methods should be retryable.
[
https://issues.apache.org/jira/browse/TS-4921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Leif Hedstrom updated TS-4921:
--
Fix Version/s: 7.1.0
> 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)
[jira] [Updated] (TS-4921) Safe HTTP methods should be retryable.
[
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)
[jira] [Updated] (TS-4921) Safe HTTP methods should be retryable.
[
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: 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 best approach is to create a config
>option (which is transaction overrideable) which allows you to define the list
>of methods which are retryable.
> 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: 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)
[jira] [Updated] (TS-4921) Safe HTTP methods should be retryable.
[
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: GET HEAD
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 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
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4921) Safe HTTP methods should be retryable.
[
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: GET HEAD
>From conversations, it sounds like the best approach is to create a config
>option (which is transaction overrideable) which allows you to define the list
>of methods which are retryable.
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
> 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
>
> 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 best approach is to create a config
> option (which is transaction overrideable) which allows you to define the
> list of methods which are retryable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TS-4921) Safe HTTP methods should be retryable.
[
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: GET HEAD
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
> 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
>
> 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
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
