Paulo Levi wrote:
Anyone read the first message at all? The problem is that other proxy
requests are effectively ignored after a DIRECT connection even if it
fails.
What i am trying right now is implementing ProxySelector so that a
"manual" proxy configuration is added at the end of the
public List<Proxy> select(final URI uri)
return list, and only requesting configuration from the user if
public void connectFailed(final URI uri, final SocketAddress sa, final
IOException ioe)
function is called.
Obviously this won't work how the current setup is done. What is so
special about direct connection requests that they must break the
proxy chain of responsibility?
That's because DIRECT means "do not use a proxy" and
ProxySelector.connectFailed() is only called when a connection to a
proxy failed so that it can, potentially, be removed from the list of
available proxies.
Since no proxy connection was attempted, the callback is not triggered
even if the connection failed.
begin:vcard
fn:Jean-Christophe Collet
n:Collet;Jean-Christophe
org:Sun Microsystems
adr:;;2 rue de Jargonnant;Geneva;;1207;Switzerland
email;internet:jean-christophe.col...@sun.com
title:Staff Engineer
x-mozilla-html:FALSE
version:2.1
end:vcard
