为什么Windows上的IE / Chrome不支持端口27977上的SOCKS5代理？ [英] Why doesn't IE/Chrome on Windows support SOCKS5 proxies on port 27977?
问题描述
我正在使用在Windows机器上使用代理的客户端。他们最近来找我解决为什么Interenet Explorer和Chrome拒绝在端口27977上使用SOCKS5代理的问题。我相信这与27977上的所有代理都是在纯SOCKS5中实现的事实有关。我可以使用Firefox中的这些代理以及Ubuntu下的Chrome来使Firefox运行良好。旁注：我的Nexus One也可以在Firefox上使用Android。我想知道如果他们是一个补丁，或者如果IE9会有更好的支持等。感谢任何帮助家伙。
解决方案将可以正常使用SOCKS5代理（它会自动检测代理的类型）。
然而，对于Chrome，您可以使用命令行强制Chrome使用SOCKS5代理，而不是尝试（和失败）从系统中定义的代理设置。
<在chrome的命令行中添加
- proxy-server =socks5：//1.2.3.4：8080 （例如通过编辑快捷方式的属性）。当然，更改
1.2.3.4:8080 转换为您应该使用的SOCKS5代理地址和端口。 I am working with a client who uses proxies on their Windows machines. They recently have come to me to solve the issue of why Interenet Explorer and Chrome refuse to use SOCKS5 proxies on port 27977. I believe it has something to do with the fact that all the proxies on 27977 are implemented in pure SOCKS5. I can get Firefox to work just fine with these proxies in Windows, as well as Chrome under Ubuntu. Sidenote: my Nexus One will work with them too on Firefox for Android. I am wondering if their is a patch, or if IE9 would have better support etc. Thanks for any help guys.
IE9 will work fine with a SOCKS5 proxy (it detects the type of proxy automatically).
For Chrome however, you can use the command line to force Chrome to use a SOCKS5 proxy rather than trying (and failing) to get its proxy settings from the ones defined for the system.
Add --proxy-server="socks5://1.2.3.4:8080 to chrome's command line (for instance by editing the properties of a shortcut).
Of course, change the 1.2.3.4:8080 to whatever SOCKS5 proxy address and port you should use.
这篇关于为什么Windows上的IE / Chrome不支持端口27977上的SOCKS5代理？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
