Feature changed by: Christoph Thiel (cthiel1)
Feature #305914, revision 14
Title: PAC support for 'system wide proxy configuration'
Info Provider: Dominique Leuenberger (dimstar)
Requested by: Dominique Leuenberger (dimstar)
The distribution now contains libproxy and we should try to make as
much use of it as possible.
A big advantage is the ability to parse PAC (Proxy AutoConfiguration)
without the need for this to be implemented in every application.
Simply linking against libproxy with it's very simple API (3 API calls,
2 without parameters) is enough to have the advantage of no longer
needing to 'guess' what proxy to use.
* You can set in yast / proxy a general proxy to be used
). This is bascially put into http_proxy
In gnome you can set user proxy configuration as:
* Use System Proxy (as configured in yast)
* Use proxy configuration (static, same options as in yast)
* Use automatic proxy configuration script
Yast lacks the option to specify a PAC script on system wide level.
This is only possible in the user sessions configuration. This made
sense as most applications don't know how to handle pac files anyway.
But with libroxy, this hurdle can be taken away from every single
application and can thus be offered. I'm glad to elaborate on
questions; I'm sure there are some :-)
#1: Jiri Srain (jsrain) (2009-06-02 10:19:21)
Dominique, I don't really understand what's needed on the YaST side
(probably mostly because of the lack of my knowledge), could you,
please, provide more informaiton on what you want to achieve (from the
YaST point of view)? Is it just writing proxy information to another
configuraiton file for libproxy?
#2: Dominique Leuenberger (dimstar) (2009-06-02 10:24:34) (reply to
That might be one case, but not even needed, as libproxy reads the
configurations from gnome/kde settings for example (current running
yast wouuld need the enhancement to allow to also set proxy
autoconfiguration as source for proxy (at this time, you can only 'hard
code' some proxy, http, https, ftp and socks. It's not possible to
define wpad and pac.
Besides that, the 'underlying' tools, like wget, aria and the like,
spawned by yast and that connect to the net, will need libproxy
support. (for aria2c there is a enhancement request open already).
#3: Jiri Srain (jsrain) (2009-06-23 09:09:43) (reply to #2)
OK, I understand what is needed for the underlying tools, but still
don't get YaST. YaST Proxy module only sets the settings into sysconfig
(just another storage for proxy information), it is task for the
applications to either get proxy info from these variables or via
libproxy, no matter how it gets it.
#4: Dominique Leuenberger (dimstar) (2009-06-23 10:05:14) (reply to
so far correct, but let's have a look at the mask Yast2 / Proxy:
The settings available are:
[ ] Enable Proxy
HTTP Proxy URL
HTTPS Proxy URL
FTP Proxy URL
[ ] Use the Same Proxy for All Protocols
No Proxy Domains
Proxy Authentication Username / Password
It is not possible in the current mask
to define a PAC URL for the
Proxy settings.(or WPAD:// for what it matters)
I hope this helps. Otherwise we can maybe discuss the matter on IRC?
#5: Jiri Srain (jsrain) (2009-06-23 10:13:21) (reply to #4)
I understand, the question is: What shall YaST do with this
information? Write it to sysconfig where almost nobody reads it?
#6: Dominique Leuenberger (dimstar) (2009-06-23 10:21:18) (reply to
It should be written to sysconfig and with the same logic appear in envvar
The envvar for PAC scripts is formatted in this way:
Optionally, it might not be wrong to also write it to the libproxy
configuration file. But this is optional and might be to much
'enforced' as opposed to the envvar.
+ #7: Christoph Thiel (cthiel1) (2009-07-16 11:44:07)
+ Novell currently doesn't have the resources to implement something like
+ this for openSUSE 11.2.