Please take a look at libproxy, which will significantly reduce the amount of code needed for implementing proxy configuration, as well as giving you other benefits.

http://code.google.com/p/libproxy/

Epiphany will just use whatever webkit will use, which is whatever libsoup will use, which probably will be the same that gvfs will use (bug 522984).

adding a dependency on the libsoup proxy bug then

the "proxy" branch of the git repo currently has two proxy-resolver backends, one using libproxy and one using gconf directly. Note that that code is very alpha. (Eg, IIRC, it hardcodes the location of libproxy as being /opt/jhbuild.)

Hhm, i'm using epiphany-svn 8211 and webkit-svn 31823 with gnome-2.22 and an internet proxy.
Http works, https doesn't.
(proxy set via gconf and env http_proxy)

*** Bug 531074 has been marked as a duplicate of this bug. ***

(In reply to comment #2)
> Epiphany will just use whatever webkit will use, which is whatever libsoup will
> use, which probably will be the same that gvfs will use (bug 522984).
> 

Does that mean curl backend is not supported by epiphany?

I've filed a tracking bug with libproxy WebKit integration at http://code.google.com/p/libproxy/issues/detail?id=7

No decision made yet on whether to go with it yet.

I'm using the soup proxy resolver with libproxy in trunk now, so this should be fixed. Closing.

Does this work with SOCKS proxies configured? Hasn't worked for me (I don't have access to a plain HTTP proxy to test against)