[Bug 78098] Re: http_proxy defined incorrectly
Alex Mauer
hawke at hawkesnest.net
Tue Feb 6 19:33:03 UTC 2007
Yes, I did. 8080 was the default value; I assumed it would be ignored
if the host was left blank. Further, using gconf-editor's "unset key"
action on /system/http_proxy/port sets it back to 8080
Through the applet I cannot completely unset the port. It gets set to 0
if I blank it out (and the gconf key /system/http_proxy/use_http_proxy
stays set)
So presumably either this applet should be changed to default to 0; or
other things (gnome-session?) should ignore the [other] settings for
http_proxy if the host is blank; or the the applet should unset the key
/system/http_proxy/use_http_proxy if the host is blank, and whatever
sets the environment variable should read the key
/system/http_proxy/use_http_proxy instead of using
/system/http_proxy/host and /system/http_proxy/port.
--
http_proxy defined incorrectly
https://launchpad.net/bugs/78098
More information about the desktop-bugs
mailing list