[ 
https://issues.apache.org/jira/browse/HTTPCLIENT-1207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joshua Spiewak updated HTTPCLIENT-1207:
---------------------------------------

    Attachment: 
Enable_sub-classes_to_modify_the_set_of_exceptions_that_are_rejected_for_retry.patch
    
> Improve extensibility of DefaultHttpRequestRetryHandler
> -------------------------------------------------------
>
>                 Key: HTTPCLIENT-1207
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1207
>             Project: HttpComponents HttpClient
>          Issue Type: Improvement
>          Components: HttpClient
>    Affects Versions: 4.2 Final
>            Reporter: Joshua Spiewak
>            Priority: Minor
>         Attachments: 
> Enable_sub-classes_to_modify_the_set_of_exceptions_that_are_rejected_for_retry.patch
>
>
> Under certain circumstances, such as when a service is behind a load 
> balancer, it is desirable for a client to retry a request after timeout, 
> rather than simply extending the timeout. This would allow the client to 
> connect to a different service behind the load balancer.
> Currently DefaultHttpRequestRetryHandler rejects four types of Exceptions for 
> retry, including InterruptedIOException, the parent class of 
> SocketTimeoutException. The attached patch collects the Exceptions into a 
> Set, and exposes the Set to sub-classes. This should allow sub-classes to 
> remove InterruptedIOException if they see fit, but still get the benefits of 
> the other logic in retryRequest, without copying the entire class.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]

Reply via email to