After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 362596 - Proxies gconf keys are inconsistent
Proxies gconf keys are inconsistent
Status: RESOLVED DUPLICATE of bug 322211
Product: gnome-control-center
Classification: Core
Component: Network
git master
Other All
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-10-16 12:52 UTC by Ali Sabil
Modified: 2011-03-02 17:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Ali Sabil 2006-10-16 12:52:33 UTC 
Please describe the problem:
The current proxy settings gconf keys are inconsistent :
/system/http_proxy/*
/system/proxy/*



Steps to reproduce:
open gconf-editor and check the proxy keys

Actual results:


Expected results:
I suggest having
/system/proxies/autoconfig
/system/proxies/autoconfig_url
/system/proxies/<protocol>/host
/system/proxies/<protocol>/port
/system/proxies/<protocol>/authenticate
/system/proxies/<protocol>/username
/system/proxies/<protocol>/password
/system/proxies/<protocol>/ignore_hosts

or something more consistent than the current scheme

Does this happen every time?
yes

Other information:
Comment 1 Thomas Wood 2007-02-10 18:43:20 UTC 
Inconsistency is a problem, but it will be even more of a problem if we change them since we will have to end up supporting two sets of gconf keys (legacy and new).
Comment 2 Ali Sabil 2007-02-28 07:23:41 UTC 
Yes I agree with you, but the problem exists and needs to be fixed, another problem is that generally the proxy setting depends on the used iface, for example the proxy can be needed when connecting using a wifi connection while not required when using an ethernet connection.

Supporting two sets of key is indeed needed, but you will be able to drop the legacy keys sooner, than if you introduce the change later.
Comment 3 Bastien Nocera 2011-03-02 17:13:03 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 322211 ***