Bug#644373: libproxy0 0.3.1-3 doesn't work with automatic proxy configuration

[Petter Reinholdtsen]

[Petter Reinholdtsen]
> It did not help.  Am I doing it wrong?

Apparently I am.  I got some help from stormer on #libproxy over at
irc.freenode.net, and he told me that libproxy no longer implement the
WPAD protocol, and since version 0.4 require a configuration backend
to return anything else than "direct://".

After some testing and reading the source, I did find a way to get the
proxy command to look up the PAC script on the web server, using the
KDE4 config backend.  This work without a running dbus session, which
the libproxy1-plugin-gsettings config backend needed.  An alternative
might be for debian to provide its own config backend to allow us to
set the proxy configuration globally.  He said SuSe had done this for
their setup already.

I run the program like this:

  KDE_FULL_SESSION=foo \
  KDEDIRS=/usr/share/debian-edu/networked-kde3 \
  _PX_DEBUG=1 \
  proxy http://www.debian.org/ 

I'm setting KDE_FULL_SESSION to some bogus value to get the kde4
config backend to kick in, and set KDEDIRS to a directory with a file
"share/config/kioslaverc" with the proxy settings I want to get WPAD
enabled.  The _PX_DEBUG=1 enable debug output from the program.

This is the content of
/usr/share/debian-edu/networked-kde3/share/config/kioslaverc:

  # - Make Konqueror automatically detect proxy settings
  # - Force proxy use through kiosk
  ###########################################################
  [Proxy Settings][$i]
  Proxy Config Script=http://wpad/wpad.dat
  ProxyType=2

When running, this is printed:

  Configuration extension is: 20kde_config_extension
  Ingored list is: 
  Config is: 
          pac+http://wpad/wpad.dat
  PAC received!
  Using pacrunner: 25mozjs_pacrunner_extension
  Pacrunner returned: DIRECT
  http://webcache:3128 direct://

Not the most elegant way to do it, but it seem to work the way I need
it to work...

To get it working, I need to install the packages
libproxy1-plugin-kconfig and libproxy1-plugin-mozjs.  I also install
libproxy1-plugin-networkmanager to make sure libproxy do not hang when
the network is unavailable.

So this look like user error, triggered by features lost in libproxy
since we started using it.

-- 
Happy hacking
Petter Reinholdtsen