Socks proxy support doesn't work anymore

[André Stösel]

I tried:
 Hostname: socks://127.0.0.1 Port: 8888 Result: Cannot connect to proxy (127.0.0.1)
 Hostname: socks://127.0.0.1/ Port: 8888 Result: Cannot connect to proxy (127.0.0.1)
 Hostname: socks://127.0.0.1:8888 Port: 8888 Result: direct connection -> settings are ignored
 Hostname: socks://127.0.0.1:8888/ Port: 8888 Result: Message Corrupt

(It works fine with curl -> it's a midori/soup issue.)

Besides the fact that the socks:// proxy support doesn't work, midori should never use a direct connection if a proxy url is specified.

PS: Personally I think it's confusing that there is a input for "Port" which isn't used for socks:// urls - it should be deactivated.

[Cris Dywan (kalikiana)]

You said "not anymore" in the bug title but not in the description. Is this a regression? There's only one set of changes there I'm aware of - did that regress socks support? Should we back it out or fix it?

I would appreciate a simple example proxy configuration to make it as easy as possible to reproduce.

[André Stösel (ivaldi)]

It isn't a regression - I wrote "not anymore" because I assumed it worked once.
Actually, I tested 0.5.1 after I opened this bug and it doesn't work with 0.5.1 either.
(According to the FAQ socks proxy are supported since 0.5.0 (but there was no git tag vor 0.5.0)).

To setup up the proxy: ssh -D PORT user@host

and your proxy is 127.0.0.1:PORT

(To confirm that the proxy works: curl --proxy socks://127.0.0.1:PORT pyit.de/ip )