apt,wget ignore $no_proxy

Bug #95929 reported by Oliver on 2007-03-25
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
wget
Unknown
Unknown
apt (Ubuntu)
Undecided
Unassigned
wget (Debian)
Confirmed
Unknown
wget (Ubuntu)
Medium
Unassigned

Bug Description

Binary package hint: apt

Hi, I'm living in a dormitory of a university, I'm running Edgy.
I'm connected to the inet over the university-network with a traffic limitation(only to external networks).
The University has a web-cache and a Ubuntu mirror server(Cache misses count for the traffic quota).
I setup the web-cache in gnome-network-preferences WITH ignore rules for the local network.

Yesterday I exceeded my quota, i wondered where all the traffic came from.
Today I run a apt-get update, this should still work because the server is in the university-net.
This is what happens :
0% [Verbinde mit www-cache.**.de (**.**.120.30)]

If I set the Proxy settings back to direct connection it works fine.

same with a wget to the uni-ftp server OVER HTTP.
Auflösen des Hostnamen »www-cache.**.de«.... XXX.XXX.120.30,
Verbindungsaufbau zu www-cache.**.de|XXX.XXX.120.30|:3128... fehlgeschlagen: No route to host.

over ftp it works fine, but as i found out $ftp_proxy is not set by gnome-network-preferences.

oliver@m:~$ echo $no_proxy
localhost,127.0.0.0/8,*.local,XXX.XXX.0.0/16,*.uni-XXX.de

oliver@m:~$ echo $http_proxy
http://www-cache.**:3128/

ftp,https,socks are not set !?

Can anybody confirm this bug?

Oliver (lobohacks) on 2007-03-25
description: updated
description: updated
Oliver (lobohacks) on 2007-03-25
description: updated
description: updated
Oliver (lobohacks) on 2007-03-26
description: updated
feclare (feclare) wrote :

Yes, it works the same in my machine.

You can solve the no_proxy problem changing it to:

~$ echo $no_proxy
localhost,127.0.0.0/8,.local,XXX.XXX.0.0/16,.uni-XXX.de

Removing * from the domains do it work.

Changed in wget:
status: Unknown → Unconfirmed
Changed in wget:
status: New → Confirmed
armo (r-mo) wrote :

Removing the * wildcards from the domains didn't work for me. The only way I can update with apt using both our local mirror and a couple of external repositories is by not setting these vars and giving the proxy settings in apt.conf. This obviously stops wget from accessing external sites.

with $http_proxy=http://proxy.XXX.uk.com:80/
and $no_proxy=localhost,127.0.0.0/8,10.XXX.XXX.0/22,.example.internal,.local

wget http://10.XXX.XXX.70:8000/mirror/security.ubuntu.com/ubuntu/dists/hardy-security/multiverse/binary-amd64/Packages.gz
--09:19:42-- http://10.XXX.XXX.70:8000/mirror/security.ubuntu.com/ubuntu/dists/hardy-security/multiverse/binary-amd64/Packages.gz
           => `Packages.gz.1'
Resolving proxy.XXX.uk.com... XX.XX.XX.XX
Connecting to proxy.XXX.uk.com|XX.XX.XX.XX|:80... connected.
Proxy request sent, awaiting response... 403 Forbidden
09:19:42 ERROR 403: Forbidden.

apt-get update gives
...
Err http://10.XX.XX.70 hardy-security/multiverse Packages
  403 Forbidden
Ign http://ppa.launchpad.net hardy Release.gpg
...

armo (r-mo) on 2008-09-15
Changed in apt:
status: New → Confirmed
Daniel T Chen (crimsun) on 2008-09-30
Changed in wget:
importance: Undecided → Medium
Fail2Ban (failtoban) wrote :

"Launchpad doesn't support importing bugs from Savane bug trackers." --> switching to manual...

Changed in wget:
importance: Unknown → Undecided
status: Unknown → New
importance: Undecided → Unknown
status: New → Unknown
importance: Unknown → Undecided
status: Unknown → New
status: New → Fix Committed
Mitch Towner (kermiac) wrote :

@ Fail2Ban please do not change upstream bug tasks as they are used to track the progress of this bug upstream.
Thanks in advance!

Changed in wget:
importance: Undecided → Unknown
status: Fix Committed → Unknown
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.