libproxy PAC breakage

[Sam Varshavchik]

Athmane Madjoudj writes:

> On 06/26/2011 01:35 PM, Sam Varshavchik wrote:
> > libproxy is not picking up my WPAD-based config:
> >
> > [mrsam at monster ~]$ _PX_DEBUG=1 proxy http://www.cnn.com
> > Using config: 22gnome_config_extension
> > Using ignore: localhost,127.0.0.0/8
> > Config is: wpad://
> > Trying to find the PAC using WPAD…
> > WPAD search via: 24dns_alias_wpad_extension
> > PAC found!
> > Unable to find a required pacrunner!
> > direct://
> >
> > It's getting my PAC, but libproxy chokes on it. Looking at the
> > libproxy's rpm, it appears that all the javascript-related is disabled.
> >
> > Am I missing something, or is libproxy's PAC support broken?
> >
>
> Try to downgrade libproxy, it might be related to recent libproxy update.
>
> su -c 'yum downgrade libproxy*'

This was 0.4.6. Same results with 0.4.7. As I said, I looked into libproxy's  
RPM, and looks to me like PAC support could not possibly work at all, since  
all the Javascript-related support has been compiled out.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
Url : http://lists.fedoraproject.org/pipermail/users/attachments/20110626/c537cb92/attachment.bin