[
https://issues.apache.org/jira/browse/HTTPCLIENT-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17038336#comment-17038336
]
Oleg Kalnichevski commented on HTTPCLIENT-2051:
-----------------------------------------------
[~michael-o] There is also this passage.
{noformat}
Over 10 years later, most user agents still do method
rewriting for 301 and 302; therefore, this specification makes
that behavior conformant when the original request is POST.
{noformat}
Would it be OK with you if HttpClient still changed POST to GET for 301, 302
and 303. Other unsafe methods would be redirected as is.
https://github.com/apache/httpcomponents-client/pull/212
Oleg
> RedirectExec always changes HTTP method on 301, 302, 303
> --------------------------------------------------------
>
> Key: HTTPCLIENT-2051
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-2051
> Project: HttpComponents HttpClient
> Issue Type: Bug
> Components: HttpClient (classic)
> Affects Versions: 5.0 Beta7
> Reporter: Michael Osipov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> While working on WAGON-570 I noticed that {{RedirectExec}} still sticks to
> the old scheme to change request method from {{X}} to {{GET}}.
> I may understand this for 303, but not for the rest. RFC 7231 says:
> bq. Note: For historical reasons, a user agent MAY change the request method
> from POST to GET for the subsequent request. If this behavior is undesired,
> the 307 (Temporary Redirect) status code can be used instead.
> I would assume that the default behavior would *not* change the HTTP method.
> I'd expect this to be configurable on client or request basis.
> Am I misinterpreting the RFC?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
