After an evaluation, the migration from Bugzilla to GitLab is ongoing. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore. Some older issues are still tracked here (until migrated to Gitlab).
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 648237 - proxy settings have unused keys
proxy settings have unused keys
Status: RESOLVED FIXED
Product: gsettings-desktop-schemas
Classification: Core
Component: general
3.0.x
Other Linux
: Normal normal
: ---
Assigned To: gsettings-desktop-schemas-maint
gsettings-desktop-schemas-maint
:
: 657515 (view as bug list)
Depends on:
Blocks:
  Show dependency tree
 
Reported: 2011-04-19 17:46 UTC by Dan Winship
Modified: 2017-06-06 08:55 UTC (History)
2 users (show)

See Also:
GNOME target: ---
GNOME version: ---


Attachments
proxy: update documentation (3.72 KB, patch)
2011-06-06 13:40 UTC, Dan Winship
committed Details | Review

Description Dan Winship 2011-04-19 17:46:36 UTC
Two of the keys in org.gnome.system.proxy are never set by gnome-control-center, or read by glib-networking:

    - "use-same-proxy". Regardless of the setting of this key, the
      behavior is:

          - If mode is auto, then the automatic proxy URL is used
            to look up proxies for all protocols

          - If a manual https or ftp proxy is configured, it is used for
            https/ftp

          - If a manual http proxy is configured, it is used for http,
            and also for https if no https proxy is configured

          - If a manual SOCKS proxy is configured, it is used for all
            protocols, except where that would conflict with the above.

    - "http/enabled". This is redundant/asymmetric; none of the other
      child schemas have their own enabled flag, and are simply enabled/
      disabled automatically based on whether or not the host field is
      non-empty and the port is non-0, so http should work the same way
      as well.

Of course, simply removing these from the schema would cause crashes in any apps that were mistakenly reading them. I guess the fix is to change the doc strings to mark them as deprecated, but that would be post-branch because of string freeze.
Comment 1 Dan Winship 2011-06-06 13:40:14 UTC
Created attachment 189322 [details] [review]
proxy: update documentation

In particular, note that /system/proxy/use-same-proxy and
/system/proxy/http/enabled are not actually used.
Comment 2 Christian Persch 2011-06-06 14:51:08 UTC
   <schema id="org.gnome.system.proxy.http" path="/system/proxy/http/">
     <key name="enabled" type="b">
       <default>false</default>

IMHO should also change the default to true, here.
Comment 3 Dan Winship 2011-08-28 13:30:54 UTC
*** Bug 657515 has been marked as a duplicate of this bug. ***
Comment 4 Dan Winship 2011-08-28 13:33:15 UTC
(In reply to comment #2)
>    <schema id="org.gnome.system.proxy.http" path="/system/proxy/http/">
>      <key name="enabled" type="b">
>        <default>false</default>
> 
> IMHO should also change the default to true, here.

I don't think that's any better; any code that is looking at this key is just wrong. Changing the default would just mean that some apps might insist on always using a proxy even when they shouldn't, rather than never using a proxy even when they should.
Comment 5 Dan Winship 2011-08-30 14:45:02 UTC
Attachment 189322 [details] pushed as 6cfbb00 - proxy: update documentation
Comment 6 Antonin 2017-06-06 08:55:12 UTC
Hi I don't know if this is really the right place to post as a user, but using gnome Network / Network proxy applet, When I set for instance HTTPS proxy to 'http://proxy', the exported proxy in the terminal is 'http://http://proxy:8080/
'.

Note You need to log in before you can comment on or make changes to this bug.