NEW 222374
[GTK] Consider adding support for socks5h:// proxying 
https://bugs.webkit.org/show_bug.cgi?id=222374
Summary [GTK] Consider adding support for socks5h:// proxying
Haelwenn (lanodan) Monnier
Reported 2021-02-24 11:52:11 PST
Currently WebKitGTK (probably because of one library in the libsoup/glib-networking/libproxy stack) doesn't have support for socks5h, which means that DNS resolving through SOCKS isn't supported, which prevents usage of things like Tor to work properly (there is workarounds but I wouldn't really depend on that).
Attachments
Add attachment proposed patch, testcase, etc.
Carlos Garcia Campos
Comment 1 2021-02-24 23:03:26 PST
Yes, we simply pass a GProxyResolver to libsoup, so it's in gli/glib-networking where the support should be added. I guess there's not much we can do in WebKit.
Michael Catanzaro
Comment 2 2021-02-25 08:03:31 PST
GProxyResolver isn't designed to handle DNS, though. You might be looking at a total rethink of the boundaries between GResolver and GProxyResolver? I'm not sure. Certainly this needs to be addressed at the glib level. libsoup and WebKit are much higher-level. (Mildly-related: if you care about proxies, nobody knows how they are supposed to work: https://gitlab.gnome.org/GNOME/glib/-/issues/2291.)
Haelwenn (lanodan) Monnier
Comment 3 2021-02-25 16:08:34 PST
Thanks for the mildly-related issue. At least in the case of socks, specially with introducing the socks5h/non-socks5h distinction it should be non-ambiguous. And with using `http_proxy`, `HTTPS_PROXY`, `${PROTOCOL}_PROXY` and `ALL_PROXY` like is done in `curl`'s environment variables (btw that's the way I'm doing it for everything as a non-DE user) might help even further on this.
Note You need to log in before you can comment on or make changes to this bug.