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 502103 - libsoup should use libproxy
libsoup should use libproxy
Status: RESOLVED FIXED
Product: libsoup
Classification: Core
Component: Misc
unspecified
Other All
: Normal enhancement
: ---
Assigned To: libsoup-maint@gnome.bugs
libsoup-maint@gnome.bugs
Depends on:
Blocks:
 
 
Reported: 2007-12-06 16:38 UTC by Nathaniel McCallum
Modified: 2010-11-12 23:12 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Nathaniel McCallum 2007-12-06 16:38:30 UTC 
libsoup should use libproxy to gain all kinds of auto-magic proxy goodness.

http://code.google.com/p/libproxy/
Comment 1 Alex Panait 2007-12-20 17:21:42 UTC 
libproxy 0.2 was released.
Comment 2 Dan Winship 2008-01-15 18:00:41 UTC 
I think I'm planning to do this at some point btw, just not sure exactly when.
Comment 3 Dan Winship 2008-11-04 21:54:18 UTC 
libsoup now optionally uses libproxy. it will become mandatory if libproxy is accepted as an external dependency
Comment 4 David Woodhouse 2010-11-12 23:12:21 UTC 
This isn't working very well. The PacRunner dæmon has a reimplementation of libproxy, which *just* sends a D-Bus request to PacRunner rather than reloading the PAC file in every single application, etc.

But because of all the problems with the original libproxy, the code in libsoup isn't actually *calling* into libproxy in a lot of circumstances. Can we make it detect the pacrunner-libproxy implementation and actually *use* it? Or perhaps just communicate directly with PacRunner over D-Bus instead?