Comment #10 on issue 12303 by benizi: Chrome falls back to DIRECT
connections once all proxies have failed.
http://code.google.com/p/chromium/issues/detail?id=12303
I'm complaining about this. :-)
As a use case where this behavior does matter:
I use proxy.pac to send personal sites through an SSH SOCKS5 proxy, since
I'm on
unencrypted wifi. e.g.:
function FindProxyForURL(url, host) {
var benizi = "SOCKS5 127.0.0.1:23649";
var direct = "DIRECT";
if (
/facebook/i.test(url)
|| /fbcdn/i.test(url)
|| /myspace/i.test(url)
|| /friendster/i.test(url)
)
return benizi;
return direct;
}
I know it's insecure after it reaches the other end of the SSH tunnel, but
at least
I'm avoiding having traffic sent unencrypted over wifi. When my SSH tunnel
fails,
Chromium happily does that.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
