[
https://issues.apache.org/jira/browse/HTTPCLIENT-1176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875799#comment-13875799
]
Sivasubramaniam S commented on HTTPCLIENT-1176:
-----------------------------------------------
I am working on this improvement and I need answers for the following question
to proceed -
I understand that when the first proxy is unreachable, the subsequent proxy (if
it is reachable) must be chosen. I would like to know the expected behavior
when all the proxies in the list returned by ProxySelector.select() are
unreachable. Should a direct connection be used or should the first proxy be
selected again leading to failure on socket errors (the current behavior)?
> Support proxy failover per ProxySelector API
> --------------------------------------------
>
> Key: HTTPCLIENT-1176
> URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1176
> Project: HttpComponents HttpClient
> Issue Type: Improvement
> Components: HttpConn
> Affects Versions: 4.2 Beta1
> Environment: All supported platforms/environments which use proxy
> failover
> Reporter: Jan-Willem Maarse
> Priority: Minor
> Fix For: 4.4 Final
>
>
> The ProxySelectorRoutePlanner selects a single proxy from the list returned
> by the java.net.ProxySelector API. If the client can't open a socket to the
> proxy, other proxies in the list are ignored and the request fails. It would
> be good if the Apache HttpClient could try other proxies in the list before
> failing on socket errors. HttpURLConnection provides similar behavior. This
> functionality is useful in network configurations where proxies can go up and
> down for maintenance, for example.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
