Comment #97 on issue 266 by cstratton: Chrome uses Windows' proxy settings
http://code.google.com/p/chromium/issues/detail?id=266
I'm trying to use the --proxy-server command-line option for Chrome, but it
doesn't
seem to be working correctly for me. I'm setting up my proxy using PuTTY
("plink.exe
[email protected] -D 9090"). I can then get the proxy working successfully
by changing
the Windows Internet Options to set a system-wide proxy at 127.0.0.1:9090,
but this
only works if the SOCKS proxy is the only one set; all others
(HTTP/Secure/GTP) must
be left blank, or else I can't connect to anything. I'd rather only use
the proxy
for Chrome, so I've been experimenting with "chrome.exe
--proxy-server=127.0.0.1:9090", but that won't connect to anything either.
Is it
possible that the --proxy-server flag is setting the server for all
protocols, and if
so, is there a separate flag to set just the SOCKS proxy?
(I'm running Chrome 3.0.193.2 from the Beta channel on Windows XP, fwiw)
--
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
-~----------~----~----~----~------~----~------~--~---
