[Webkit-unassigned] [Bug 111257] WebKitGTK fails to connect via HTTP if only SOCKS proxy is specified, but connects to HTTPS

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=111257





--- Comment #1 from Christian Stadelmann <wk at genodeftest.de>  2013-03-02 15:35:31 PST ---
For every HTTP-only URL webkit tries to load tor (the SOCKS proxy I currently use) logs:
~~~~~
[notice] Application asked to connect to port 0. Refusing.
[warn] socks4: Port or DestIP is zero. Rejecting.
[warn] Fetching socks handshake failed. Closing.
[warn] socks4: Port or DestIP is zero. Rejecting.
[warn] Fetching socks handshake failed. Closing.
~~~~~

Seems like webkitgtk or libsoup read all proxy settings and ignore that (according to the GSettings Schema http://git.gnome.org/browse/gsettings-desktop-schemas/tree/schemas/org.gnome.system.proxy.gschema.xml.in.in ) an empty host name or a port number 0 disables the proxy for that protocol. In other words: the data read from org.gnome.system.proxy.* is misinterpreted.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.