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 616825 - Network Proxy Preferences sets $no_proxy incorrectly, that misleads wget
Network Proxy Preferences sets $no_proxy incorrectly, that misleads wget
Status: RESOLVED DUPLICATE of bug 609459
Product: gnome-terminal
Classification: Core
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-04-26 07:44 UTC by Kentaro Fukuchi
Modified: 2010-05-01 18:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Kentaro Fukuchi 2010-04-26 07:44:57 UTC
Probably this is not error of ’Network Proxy Preferences', but I'm not sure what component is related to this bug.

Open 'Network Proxy Preferences' and select the 'Ignored Hosts' tab. Add a couple of hostnames to the list then close the window. Open a new shell and type "echo $no_proxy". Here I pasted mine.

$ echo $no_proxy 
localhost,127.0.0.0/8,*.local,
$

As shown above, it has a trailing comma. I checked /system/http_proxy/ignore_hosts with gconf-editor, but it was correctly configured ( "[localhost,127.0.0.0/8,*.local]" ).

Usually it does not cause any problem, but wget is affected. When $no_proxy has a trailing comma, wget does not use proxy to connect to any hosts, even if they are not listed in the $no_proxy. When I gave $no_proxy without the comma to wget manually, it perfectly worked.
Comment 1 Jens Granseuer 2010-05-01 18:25:16 UTC
I think that's gnome-terminal.
Comment 2 Christian Persch 2010-05-01 18:41:49 UTC

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