[Bug 1575877] Re: no_proxy ignored if https_proxy set

Launchpad Bug Tracker 1575877 at bugs.launchpad.net
Tue May 24 21:00:37 UTC 2016


This bug was fixed in the package apt - 1.0.1ubuntu2.14

---------------
apt (1.0.1ubuntu2.14) trusty; 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 <pc at pcable.net>  Tue, 17 May 2016 13:45:06 -0700

** Changed in: apt (Ubuntu Trusty)
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 Committed

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



More information about the foundations-bugs mailing list