[
https://issues.apache.org/jira/browse/HTTPASYNC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski updated HTTPASYNC-33:
---------------------------------------
Fix Version/s: 4.0-beta4
Blocking HttpClient re-throws HttpExceptions as ClientProtocolException for
historical reasons (compatibility with older HttpClient versions). I do not
think that HttpAsyncClient needs to do likewise. So, it is a matter of
documenting the difference in behavior.
Oleg
> Syncronous and asynchronous versions of the client report exception in a
> slightly different way
> -----------------------------------------------------------------------------------------------
>
> Key: HTTPASYNC-33
> URL: https://issues.apache.org/jira/browse/HTTPASYNC-33
> Project: HttpComponents HttpAsyncClient
> Issue Type: Task
> Reporter: Sebastiano Vigna
> Priority: Minor
> Fix For: 4.0-beta4
>
>
> This is more a "surprising behaviour" report than a true bug report. We
> noticed that if you use the asynchronous client and perform too many
> redirects, the exception passed to the FutureCallback is a RedirectException.
> However, if you use the synchronous client the execute() method throws a
> ClientProtocolException whose cause is a RedirectException. If this behaviour
> is intended it should be probably documented.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
