Status: Unconfirmed Owner: ---- Labels: Type-Bug Pri-2 OS-All Area-Misc New issue 18142 by bottiger1: Socks http://code.google.com/p/chromium/issues/detail?id=18142
Chrome Version : Google Chrome 3.0.196.0 (Official Build 22005) WebKit 532.0 V8 1.2.14.14 User Agent Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US) AppleWebKit/532.0 (KHTML, like Gecko) Chrome/3.0.196.0 Safari/532.0 What steps will reproduce the problem? 1. Use a socks proxy setting. 2. Go to any website. What is the expected result? Chrome is supposed to have socks4a which means DNS requests do not leak and are forwarded to the proxy. What happens instead? DNS requests leak. Someone told me that socks4a is only enabled when the host name fails to resolve. So I used my firewall to block port 53 (DNS). But then chrome stopped working and I couldn't visit any websites at all. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
