This bug was fixed in the package apt - 1.0.10.2ubuntu3 --------------- apt (1.0.10.2ubuntu3) wily; urgency=medium
* When using the https transport mechanism, $no_proxy is ignored if apt is getting it's proxy information from $https_proxy (as opposed to Acquire::https::Proxy somewhere in apt config). If the source of proxy information is Acquire::https::Proxy set in apt.conf (or apt.conf.d), then $no_proxy is honored. This patch makes the behavior similar for both methods of setting the proxy. (LP: #1575877) -- Patrick Cable <p...@pcable.net> Wed, 18 May 2016 08:09:20 -0700 ** Changed in: apt (Ubuntu Wily) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1575877 Title: no_proxy ignored if https_proxy set Status in apt package in Ubuntu: Fix Released Status in apt source package in Precise: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Wily: Fix Released Bug description: Description: When using the https transport mechanism, $no_proxy is ignored if apt is getting it's proxy information from $https_proxy. If the source of proxy information is Acquire::https::Proxy set in apt.conf (or apt.conf.d), then $no_proxy is honored. Package Versions: 1.0.1ubuntu2.13 on 14.04 LTS 1.2.10ubuntu1 on 16.04 LTS Expected result: Apt would pull down my packages from my internal repository without trying to put it through the proxy. I've submitted a patch upstream that seems to fix the behavior, see https://github.com/Debian/apt/pull/14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1575877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp