Chrome not respecting "no_proxy" on Linux
Reported by
3095185...@qq.com,
Aug 2
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.99 Safari/537.36 Example URL: Steps to reproduce the problem: 1. local ipaddress=10.10.1.1 2. open /etc/profile 3. config proxy: http_proxy,https_proxy, no_proxy="10.10.*" 4. install apache2 5. open chrome browser, input URL:"http://127.0.0.1", is ok,show appache page. 6. input URL:"http://10.10.1.1"，no return, is waiting. What is the expected behavior? expect chrome can match no_proxy like "10.10.*" firefox use proxy setting by itself, no_proxy setting "10.10.*", it is ok. What went wrong? chrome use system proxy setting , but can not match n_proxy like "10.10.*" Did this work before? N/A Chrome version: 67.0.3396.99 Channel: stable OS Version: 16.04 LTS Flash Version:
,
Aug 2
,
Aug 2
Wildcards in the proxy bypass list work fine. I expect the issue here is that environment variables do not have precedence over desktop environment proxy settings (say gsettings). So you will need to set your bypass list in for instance the gnome settings. Or one of the many other mechanisms (chrome policy, extension, command line switch --proxy-bypass-list). |
|||
►
Sign in to add a comment |
|||
Comment 1 by mmenke@chromium.org
, Aug 2