[
https://issues.apache.org/jira/browse/TS-3656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14579048#comment-14579048
]
Sudheer Vinukonda edited comment on TS-3656 at 6/9/15 3:58 PM:
---------------------------------------------------------------
Do we claim to support redirection for POST? POST is not an idempotent method
and AFAIK, it is highly unreliable and not recommended to use redirection with
POST method. See below link for more details:
http://www.alanflavell.org.uk/www/post-redirect.html
There was even an explicit note related to this, in the older version RFC2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3
{code}
10.3 Redirection 3xx
This class of status code indicates that further action needs to be taken by
the user agent in order to fulfill the request. The action required MAY be
carried out by the user agent without interaction with the user if and only if
the method used in the second request is GET or HEAD.
{code}
Note that, that restriction seems to have been removed from the newer bis
version, but, I'd still be careful in claiming support for redirection with
POST, and even then, it should be done as a feature evaluating the current
design etc.
http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-26#section-6.4
was (Author: sudheerv):
Do we claim to support redirection for POST? POST is not an idempotent method
and AFAIK, it is highly unreliable and not recommended to use redirection with
POST method. See below link for more details:
http://www.alanflavell.org.uk/www/post-redirect.html
There was even an explicit restriction to that effect in the older version
RFC2616
http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3
{code}
10.3 Redirection 3xx
This class of status code indicates that further action needs to be taken by
the user agent in order to fulfill the request. The action required MAY be
carried out by the user agent without interaction with the user if and only if
the method used in the second request is GET or HEAD.
{code}
Note that, that restriction seems to have been removed from the newer bis
version, but, I'd still be careful in claiming support for redirection with
POST, and even then, it should be done as a feature evaluating the current
design etc.
http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-26#section-6.4
> Activating follow redirection in send server response hook does not work for
> post
> ---------------------------------------------------------------------------------
>
> Key: TS-3656
> URL: https://issues.apache.org/jira/browse/TS-3656
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Susan Hinrichs
> Assignee: Susan Hinrichs
> Fix For: 6.0.0
>
>
> If you have a plugin on the TS_HTTP_SEND_RESPONSE_HDR_HOOK, calls
> TSHttpTxnFollowRedirect(txn, 1), redirecting a POST request will fail.
> In the not so bad case, the POST request will be redirected to the new
> location, but the POST data will be lost.
> In the more bad case, ATS will crash.
> The issue is that the post_redirect buffers are freed early on. One could
> delay the post_redirect deallocation until later in the transaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
