GNOME Bugzilla – Bug 703854
GProxyResolver doesn't report error when PAC fails due to missing PAC module
Last modified: 2018-05-29 06:42:34 UTC
When configuring system wide proxy settings with an Proxy Auto-Config-File (.pac), proxy servers in the .pac file are not used. Reproducible on Arch Linux.
I have the same problem on debian jessie. When I configure the proxy manually, epiphany works. When I configure the proxy automatically using the .pac file, it does not work. Note that when using firefox and configuring the proxy automatically using the same .pac file, it *does* work.
Hi, how do you "configure system wide proxy settings with an Proxy Auto-Config-File?" Please provide specific steps.
In gnome settings, choose "network", then "proxy" and "automatic". Then enter the address of the .pac file.
OK... Epiphany doesn't have anything to do with that. I will move this to libsoup to be conservative, but I guess it's an enhancement request for gio.
PAC works fine on Fedora... does glib-pacrunner get started after you set "automatic" proxy mode and then try to connect to something? I'm guessing probably the problem is that you don't have either of the two libproxy pacrunner modules installed (eg, on Fedora 21, /usr/lib64/libproxy/0.4.11/modules/pacrunner_mozjs.so). Presumably due to how the libproxy package is split up on arch/debian. Can you confirm that installing either the mozjs or the webkit libproxy pacrunner module fixes things? If so, we need to figure out some way to get an error message out here rather than just failing silently...
On my debian jessie system, I just remarked that the libproxy1-plugin-webkit and libproxy1-plugin-gsettings packages are not installed. Maybe this is the reason why epiphany does not work with automatic proxy configuration? Sorry, I cannot test the software before September, since I am out of my lab for the summer.
Actually, I was able to test the proxy configuration using VPN. So I confirm that now, on my debian Jessie system, epiphany works with an automatic proxy configuration after I installed libproxy1-plugin-webkit. Therefore, I will report this problem to debian. Thanks for the help.
OK. It's still a glib bug too though because we really ought to be able to report this error in some way... Maybe just have gnome-control-center check for it...
*** Bug 751370 has been marked as a duplicate of this bug. ***
The corresponding debian bug has been reported here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=789630
Unfortunately, libproxy doesn't return any error in this case (and in fact, has no way to return errors in its API). So this will likely stay broken until bug 659857 is implemented.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/728.
Reopening. This bug was migrated to https://gitlab.gnome.org/GNOME/glib, but it should have been migrated to https://gitlab.gnome.org/GNOME/glib-networking.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib-networking/issues/22.