I'm seeing this issue with correctly working no_proxy settings via
/etc/environment and/or /root/.bashrc,
which are correctly working for e.g. w3m but are not honored via
apt-transport-https.
Running Debian Wheezy,
apt 0.9.7.9+deb7u2
apt-transport-https 0.9.7.9+deb7u2
apt-utils 0.9.7.9+deb7u2
I'm using:
# env | grep proxy
http_proxy=http://proxy:8080
ftp_proxy=http://proxy:8181
https_proxy=http://proxy:8080
no_proxy=myserver.domain.tld,
relevant sources.list:
deb https://myserver.domain.tld/debian/ /
"apt-get update -o Debug::Acquire::Https=true"
still shows that APT is trying to use the proxy.
The following configuration via /etc/apt/apt.conf.d/proxy.conf does the
trick:
# Platform Specific Proxy Configuration
Acquire::Http::Proxy "http://proxy:8080";;
Acquire::Https::Proxy "http://proxy:8080";;
Acquire::Ftp::Proxy "http://proxy:8181";;
# DIRECT Access for myserver.domain.tld
Acquire::Https::Proxy::myserver.domain.tld "DIRECT";
Cheers,
Raoul
PS. Please let me know in case I should file a new bug report.
--
DI (FH) Raoul Bhatia M.Sc. | E-Mail. ra...@bhatia.at
Software Development and | Web. http://raoul.bhatia.at/
System Administration | Tel. +43 699 10132530
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
