Issue metadata
Sign in to add a comment
|
Not honouring System Proxy in case of proxy url
Reported by
nimitag...@gmail.com,
Dec 11
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36 Steps to reproduce the problem: If I start my chrome 71 with --proxy-pac-url then the loopback URL(localhost, 127.0.0.1) does not follow the system proxy in Windows. Step to reproduce - Set up a proxy, be sure to exclude localhost from bypass Then open the chrome with a random pac file, then open a localhost or 127.0.0.1 It would not go through the proxy and will open directly. What is the expected behavior? In chrome 70 the --proxy-pac-url used, didnt effect the loopback addresses What went wrong? If I start my chrome 71 with --proxy-pac-url then the loopback URL(localhost, 127.0.0.1) does not follow the system proxy in Windows. Did this work before? Yes 70 Chrome version: 71.0.3578.80 Channel: stable OS Version: 10 Flash Version:
,
Dec 11
This unfortunately was a deliberate change to address a security issue. Ideally we'd add some explicit way to opt-in to allowing proxying localhost when using a PAC script.
,
Dec 11
We could add something like --proxy-pac-bypass-list= as an analogous flag to --proxy-bypass-list, for the command line invocation case. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Dec 11