Bug 288002

I definitely can reproduce the issue, but this is not a KDE problem. We do not provide such integration.

In corresponding bug for Chromium ( http://code.google.com/p/chromium/issues/detail?id=106052#c6 ), somebody noted that the format of how KDE saves the proxy host has changed:

"KDE 4.8 saved the PROXY address as (e.g.) 

http://proxyhost 8080

Where KDE 4.7* and before saved it, quite obviously, as
http://proxyhost:8080"

If the format really has changed in KDE 4.8, won't there be other applications that are broken now?

(In reply to comment #2)
> In corresponding bug for Chromium (
> http://code.google.com/p/chromium/issues/detail?id=106052#c6 ), somebody noted
> that the format of how KDE saves the proxy host has changed:
> 
> "KDE 4.8 saved the PROXY address as (e.g.) 
> 
> http://proxyhost 8080
> 
> Where KDE 4.7* and before saved it, quite obviously, as
> http://proxyhost:8080"

Yes and that was done for a reason. A white space is not a valid URL character where as a ':' is. And I made this change because in KDE 4.8's proxy configuration dialog we need to know whether or not the user entered protocol information, e.g. http://, when typing in the proxy information.

> If the format really has changed in KDE 4.8, won't there be other applications
> that are broken now?

If those other applications were reading the configuration file directly, then yes they would be broken. We have an API to access proxy information and as such we make no guarantees that the configuration file format would be kept compatible forever. There is always a possibility for any configuration file to change in the future.

I allowed myself to relay this to http://code.google.com/p/chromium/issues/detail?id=106052#c10

I'm using KDE 4.13 and looks like this settings was reverted

cat `kde4-config --localprefix`/share/config/kioslaverc
ProxyUrlDisplayFlags=8

[$Version]
update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.2/r3

[Proxy Settings]
NoProxyFor=
Proxy Config Script=
ProxyType=1
ReversedException=false
ftpProxy=
httpProxy=
httpsProxy=
socksProxy=http://127.0.0.1 1080

Now chromium can't read this settings (rekonq still can)

(In reply to comment #5)
> I'm using KDE 4.13 and looks like this settings was reverted
> 
> cat `kde4-config --localprefix`/share/config/kioslaverc
> ProxyUrlDisplayFlags=8
> 
> [$Version]
> update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.
> 2/r3
> 
> [Proxy Settings]
> NoProxyFor=
> Proxy Config Script=
> ProxyType=1
> ReversedException=false
> ftpProxy=
> httpProxy=
> httpsProxy=
> socksProxy=http://127.0.0.1 1080
> 
> Now chromium can't read this settings (rekonq still can)

I do not understand what you are saying here. We did not revert anything. The proxy configuration information has been this way since KDE 4.8. See comment#2 and comment#3.

(In reply to comment #6)
> (In reply to comment #5)
> > I'm using KDE 4.13 and looks like this settings was reverted
> > 
> > cat `kde4-config --localprefix`/share/config/kioslaverc
> > ProxyUrlDisplayFlags=8
> > 
> > [$Version]
> > update_info=kioslave.upd:kde2.2/r1,kioslave.upd:kde2.2/r2,kioslave.upd:kde2.
> > 2/r3
> > 
> > [Proxy Settings]
> > NoProxyFor=
> > Proxy Config Script=
> > ProxyType=1
> > ReversedException=false
> > ftpProxy=
> > httpProxy=
> > httpsProxy=
> > socksProxy=http://127.0.0.1 1080
> > 
> > Now chromium can't read this settings (rekonq still can)
> 
> I do not understand what you are saying here. We did not revert anything.
> The proxy configuration information has been this way since KDE 4.8. See
> comment#2 and comment#3.

Yes, your right.  Sorry,  first time I didn't understand right #3. Looks like it something wrong with chromium, not KDE