Details
-
Task
-
Status: Resolved
-
Minor
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
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.