Feature Request: Add option like firefox network.proxy.socks_remote_dns to True
Reported by
hufeng1...@gmail.com,
Sep 8 2017
|
||
Issue descriptionFeature Request: Add option like firefox network.proxy.socks_remote_dns to True The current chrome with socks5 proxy will not resolve dns over socks5 proxy, And the dns resolve very slow. Please add an options like firefox network.proxy.socks_remote_dns to True to resolve dns over socks5 proxy, it will help us to navigate the web bypass the China Great Firewall.
,
Sep 8 2017
When using a socks proxy, we'll let it resolve IP addresses for HTTP requests. Other DNS requests, like those initiated by PAC scripts, will not use the proxy. Are you sure you're telling chrome to use the proxy as a SOCKS5 proxy, and not as a SOCKS proxy?
,
Sep 8 2017
Chrome already behaves this way -- Using a SOCKSv5 proxy in Chrome implies socks_remote_dns=True. If you are not seeing that behavior, then you have configured it in Chrome as a v4 not v5. From a PAC script use the token "SOCKS5" not "SOCKS". If you are setting from a command-line flag you can use either socks5:// or socks://. See also https://www.chromium.org/developers/design-documents/network-stack/socks-proxy. |
||
►
Sign in to add a comment |
||
Comment 1 by sc00335...@techmahindra.com
, Sep 8 2017Components: Internals>Network>Proxy
Labels: -Type-Bug Needs-Milestone Triaged-ET OS-Linux OS-Mac OS-Windows Type-Feature
Status: Untriaged (was: Unconfirmed)