SOCKS support

[GoogleCodeExporter]

Could you enable SOCKS v5 support ?

Original issue reported on code.google.com by kerf...@gmail.com on 10 Dec 2009 at 2:19

[GoogleCodeExporter]

Unfortunately, Windows doesn't support Socks v5 natively. however I'll try to 
implement 
this feature in the upcoming releases.

Original comment by Mohamma...@gmail.com on 11 Dec 2009 at 1:14

• Changed state: Accepted
• Added labels: Usability

[GoogleCodeExporter]

It would be great to implement "hostnames resolving over SOCKS v5" feature.

Original comment by ydid...@gmail.com on 21 Dec 2009 at 11:13

[GoogleCodeExporter]

Working on SOCKS v5 support (not including DNS over SOCKS).

Original comment by Mohamma...@gmail.com on 6 Jan 2010 at 6:52

• Changed state: Started

[GoogleCodeExporter]

It looks like you can trick it into using SOCKS v5 today.

If in switchy you enter under the HTTP proxy field something like:

    Http Proxy:    socks5://localhost
    Port:          1080

Then this sets the HTTP proxy to "socks5://localhost:1080", which chrome parses 
to 
mean a SOCKS v5 proxy at "localhost:1080", and things seem to work.

I confirmed this in Chrome by navigating to "chrome://net-
internals/proxyservice.config" to see what it interpreted the settings to mean. 
(note 
that you need to do a page load first before chrome re-fetches the IE settings).

@ydidukh:
> It would be great to implement "hostnames resolving over SOCKS v5" feature.

That particular issue should have been fixed in Chromium, see 
http://crbug.com/29914 
. The fix is not yet part of the stable releases, but it will be soon, I hoope.

Original comment by eroman@chromium.org on 8 Jan 2010 at 5:10

[GoogleCodeExporter]

eroman
Your trick does not seem to work for me. I filled the fields as you wrote and 
hit
"save", and it automatically turned into this:

Original comment by xlu.2...@gmail.com on 8 Jan 2010 at 10:42

Attachments:

• 5.jpg

[GoogleCodeExporter]

@eroman
Nice trick, and a more simpler way to set Chrome's SOCKS5 proxy than using PAC 
scripts!
Thanks for the tip.

Regarding support of DNS over SOCKS: it's really great news! hope the fix is 
released 
soon, and thanks for your efforts and fixing this issue :)

Original comment by Mohamma...@gmail.com on 8 Jan 2010 at 11:14

[GoogleCodeExporter]

@xlu.2007
It works well, check "chrome://net-internals/proxyservice.config".
Anyway, the upcoming release (coming later today) will feature SOCKS v5 support.

Original comment by Mohamma...@gmail.com on 8 Jan 2010 at 11:30

[GoogleCodeExporter]

SOCKS v5 is supported now in v1.4 (sorry for the 2 days delay :)).

Original comment by Mohamma...@gmail.com on 10 Jan 2010 at 4:11

Attachments:

• SOCKSv5.png

[GoogleCodeExporter]

Original comment by Mohamma...@gmail.com on 12 Jan 2010 at 10:43

• Changed state: Fixed

[GoogleCodeExporter]

still resolve DNS locally even specified a socks5 proxy?

Original comment by electron...@gmail.com on 11 May 2010 at 2:57

[GoogleCodeExporter]

The traffic doesn't goes trough socks5 proxy after I'm entering address and 
port in corresponding field.

Original comment by dimabatm...@gmail.com on 5 Mar 2011 at 4:19

[GoogleCodeExporter]

I have the same problem: traffic doesn't go through SOCKS5. :(
And what about DNS? Is it supposed go through SOCKS5?

Original comment by borf...@gmail.com on 4 Oct 2011 at 11:00