GNOME Bugzilla – Bug 601895
SOCKS proxy doesn't work anymore
Last modified: 2015-06-02 17:19:29 UTC
Epiphany used to automatically use my SOCKS proxy specified in the gnome-network-properties. It is an SSH tunnel to secure communications over wifi hotspots and the like. Some info to reproduce/test: 1. have a machine that will be used as the remote SSH host 2. SSH into it, by running this in a terminal (keep the terminal open): ssh -v -N -D 8000 the-remote-host 3. go in gnome's proxy settings (gnome-network-properties) 4. set the mode to "manual proxy configuration" 5. set the "socks host" to localhost, port 8000 (leave the other proxy types blank) 6. make the terminal (the one with the ssh tunnel running in it) show "always on top" so you can see its activity at all times 7. use epiphany and visit websites, notice that nothing happens in the terminal. 8. use firefox/chromium-browser: notice that activity shows up in the terminal where SSH is running (new "channels" are opened, etc.), indicating that they indeed uses the socks proxy This used to work in previous versions of Epiphany, IIRC.
this is basically a dup of the corresponding libsoup bug, bug 553269, but I don't know if you want to track it separately for epiphany
Perhaps yes, that way other users looking for bugs filed on epiphany may find this one, and also because launchpad is tracking this one?
Dan: how come epiphany wasn't affected before the switch to webkit, it wasn't using libsoup? The fact that bug #553269 has been open for two years doesn't sound good, but I don't remember epiphany from >1 year ago not working with GNOME's SOCKS proxies settings.
Yes. Epiphany used to be based on gecko, so it used the mozilla networking stack, which had its own proxy handling.
I presume this is fixed, and a dup of #553269 as Dan suggested. *** This bug has been marked as a duplicate of bug 553269 ***