[Bug 1575877] Re: no_proxy ignored if https_proxy set

[Martin Pitt]

Hello Patrick, or anyone else affected,

Accepted apt into wily-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.0.10.2ubuntu3 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: apt (Ubuntu Wily)
       Status: Triaged => Fix Committed

** Tags removed: verification-done

** Tags added: verification-needed

-- 
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