Feature changed by: Dominique Leuenberger (dimstar) Feature #305914, revision 8 Title: PAC support for 'system wide proxy configuration' openSUSE-11.2: Evaluation Priority Requester: Important Projectmanager: Important Info Provider: Dominique Leuenberger (dimstar) Requested by: Dominique Leuenberger (dimstar) Description: 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. Current situation: * You can set in yast / proxy a general proxy to be used (http://foo.proxy.com:1234). This is bascially put into http_proxy envvar. 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 :-) Discussion: #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 + #1) + That might be one case, but not even needed, as libproxy reads the + configurations from gnome/kde settings for example (current running + env). + 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). -- openSUSE Feature: https://features.opensuse.org/305914