[
https://issues.apache.org/jira/browse/HTTPCLIENT-862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPCLIENT-862:
-----------------------------------------
Affects Version/s: 4.1 Alpha1
Fix Version/s: (was: 4.1 Alpha1)
4.1 Alpha2
It is an unfortunate oversight on my part. The fix is basically a one liner but
it will have until 4.1 alpha2
Oleg
> Extend the client's redirect handling interface to allow control of the
> content of the redirect
> -----------------------------------------------------------------------------------------------
>
> Key: HTTPCLIENT-862
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-862
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpClient
> Affects Versions: 4.0 Beta 2, 4.1 Alpha1
> Reporter: Ben Perkins
> Fix For: 4.1 Alpha2
>
>
> The existing RedirectHandler interface provides the ability influence which
> situations cause redirects, but gives you no control over the content of the
> redirect itself. For example, if you want the client follow the redirect of
> a POST request with a POST request to the new location, you can't do it.
> DefaultRequestDirector decides what method will be used on the redirect
> request and as of the most recent patch, it's always either a HEAD or a GET.
> One option for resolving this might be extending the RedirectHandler
> interface to be a factory for creating the redirect request object. The the
> DefaultRequestDirector could then be changed to ask the RedirectHandler to
> create the appropriate request for the situation.
> Thanks,
> Ben
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
