Chrome tries to DNS resolve IP addresses through SOCKS proxy |
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.39 Safari/537.36 Example URL: Steps to reproduce the problem: Chrome makes it difficult to to use a SOCKS proxy for all but local addresses. Let's assume you have a SOCKS5 proxy server at 192.168.1.100:1080 and a local web server at 127.0.0.1 that you want to access without the proxy. Per the guidelines at https://www.chromium.org/developers/design-documents/network-stack/socks-proxy, 1. Launch Chrome with --proxy-server="socks5://192.168.1.100:1080" --host-resolver-rules="MAP * ~NOTFOUND , EXCLUDE 192.168.1.100" --proxy-bypass-list="<local>" 2. Try to navigate to http://127.0.0.1 What is the expected behavior? The content served by the local web server should load. What went wrong? Chrome displays a nonsensical error page: > 127.0.0.1’s server IP address could not be found. > DNS_PROBE_FINISHED_NXDOMAIN Did this work before? N/A Chrome version: 63.0.3239.84 Channel: stable OS Version: Flash Version: A UI to enter SOCKS proxy settings would be much appreciated by users who switch from Firefox.
,
Dec 29 2017
Able to reproduce the issue on reported chrome version 63.0.3239.84 and on the latest canary 65.0.3306.0 using Ubuntu 14.04, Windows 10 and Mac 10.13.1 by launching chrome through terminal/command prompt with --proxy-server="socks5://192.168.1.100:1080" --host-resolver-rules="MAP * ~NOTFOUND , EXCLUDE 192.168.1.100" --proxy-bypass-list="<local>" . As the issue is seen from M50(50.0.2634.0) hence considering it as non-regression and marking it as Untriaged. Thanks!
,
Jan 2 2018
Can you please include a network log - https://dev.chromium.org/for-testers/providing-network-details Please file a separate bug for the UI request, to ensure the feature request can be routed and triaged appropriately.
,
Jan 2 2018
,
Jan 3 2018
Working as intended; your --host-resolver-rules is blocking access to 127.0.0.1. If you want to block using --host-resolver-rules, you should add an exclusion for 127.0.0.1 as well: --host-resolver-rules="MAP * ~NOTFOUND , EXCLUDE 192.168.1.100 , EXCLUDE 127.0.0.1" Or just remove --host-resolver-rules as in a typical setup. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krajshree@chromium.org
, Dec 25 2017