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 2013/01/10 10:46:12 UTC
[jira] [Moved] (HTTPASYNC-33) Syncronous and asynchronous versions
of the client report exception in a slightly different way
[ https://issues.apache.org/jira/browse/HTTPASYNC-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Oleg Kalnichevski moved HTTPCLIENT-1295 to HTTPASYNC-33:
--------------------------------------------------------
Component/s: (was: HttpClient)
Affects Version/s: (was: 4.2.2)
Workflow: jira (was: Default workflow, editable Closed status)
Issue Type: Task (was: Bug)
Key: HTTPASYNC-33 (was: HTTPCLIENT-1295)
Project: HttpComponents HttpAsyncClient (was: HttpComponents HttpClient)
> 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
>
> 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: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org