You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by "Oleg Kalnichevski (Jira)" <ji...@apache.org> on 2020/02/17 14:04:00 UTC
[jira] [Resolved] (HTTPCLIENT-2051) RedirectExec always changes
HTTP method on 301, 302, 303
[ https://issues.apache.org/jira/browse/HTTPCLIENT-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski resolved HTTPCLIENT-2051.
-------------------------------------------
Fix Version/s: 5.0 Beta8
Resolution: Fixed
[~michael-o] I cant help feeling automatic POST redirects would cause more harm than do good. Would it be all right with you to revisit the issue in 5.1 if see demand for this option?
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
> Fix For: 5.0 Beta8
>
> Time Spent: 20m
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org