[
https://issues.apache.org/jira/browse/HTTPCLIENT-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17090685#comment-17090685
]
ASF subversion and git services commented on HTTPCLIENT-2051:
-------------------------------------------------------------
Commit 7e2ea15f70fc5b47c8725a38d2916259ae21ac75 in httpcomponents-client's
branch refs/heads/HTTPCLIENT-2051 from Oleg Kalnichevski
[ https://gitbox.apache.org/repos/asf?p=httpcomponents-client.git;h=7e2ea15 ]
HTTPCLIENT-2051: corrected handling of 303 redirects
> 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
>
> Time Spent: 1h 40m
> 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]
