After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 695029 - Epiphany fails to connect via HTTP if only SOCKS proxy is specified, but connects to HTTPS
Epiphany fails to connect via HTTP if only SOCKS proxy is specified, but conn...
Status: RESOLVED FIXED
Product: epiphany
Classification: Core
Component: General
3.6.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: Epiphany Maintainers
Epiphany Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-02 21:49 UTC by Christian Stadelmann
Modified: 2013-07-01 22:49 UTC
See Also:
GNOME target: ---
GNOME version: 3.5/3.6


Description Christian Stadelmann 2013-03-02 21:49:55 UTC 
Using current Epiphany, etc. from Fedora 18

Steps to reproduce:
1. Configure a proxy in gnome-control-center only for SOCKS (e.g. tor without privoxy/polipo/…)
2. Do not enable the other proxies (no hostname, port is set to 0)
3. start epiphany, try to access some sites

What is expected:
A) All traffic should be routed through TOR via SOCKS (if Epiphany supports SOCKS which it does, at least partly)
B) (if Epiphany did not support SOCKS proxies) ignore proxy settings at all

What actually happens:
HTTPS connections work fine.
HTTP connections can not be established.

Epiphany can for example connect to https://en.wikipedia.org/wiki/Main_Page , but not to http://en.wikipedia.org/wiki/Main_Page
Comment 1 Christian Stadelmann 2013-03-02 22:33:25 UTC 
Sorry, this seems to be a bug in webkitgtk, since liferea (RSS Reader using webkitgtk) and eclipse (using webkitgtk) have the same problem. I filed it in https://bugs.webkit.org/show_bug.cgi?id=109350

This may or may not be related to https://bugzilla.gnome.org/show_bug.cgi?id=601895 , https://bugzilla.gnome.org/show_bug.cgi?id=553269 , https://bugzilla.gnome.org/show_bug.cgi?id=578309
Comment 2 Christian Stadelmann 2013-07-01 22:49:57 UTC 
Seems to be fixed in Fedora 19 using Gnome 3.8.

I'm closing this bug since no one seems to have it reproduced.