[Bug 1908136] Re: no_proxy=::1 is not honored by curl in Bionic and earlier versions

Balint Reczey 1908136 at bugs.launchpad.net
Tue Dec 15 19:43:12 UTC 2020


Maybe it was just a coincidence, but those regressions disappeared
immediately when reverting the ::1 addition:

LP: #1907959
https://autopkgtest.ubuntu.com/packages/s/samtools/bionic/amd64

LP: #1907955
https://autopkgtest.ubuntu.com/packages/r/ruby2.5/bionic/amd64

Since you are around would you be so kind and address @laney's more than wone yeare old comments in the following MR so the cowboy deployed can be dropped and does not make extra work for @laney to land fixes? 
https://code.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/376587

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1908136

Title:
  no_proxy=::1 is not honored by curl in Bionic and earlier versions

Status in Auto Package Testing:
  New
Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Xenial:
  New
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  Bionic:

  env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Could not resolve proxy: foo
  * Closing connection 0
  curl: (5) Could not resolve proxy: foo

  Focal:

  $ env no_proxy=::1 http_proxy=http://foo:8080 curl -v http://[::1]:80/bar.html
  * Uses proxy env variable no_proxy == '::1'
  *   Trying ::1:80...
  * TCP_NODELAY set
  * Immediate connect fail for ::1: Network is unreachable
  * Closing connection 0
  curl: (7) Couldn't connect to server

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1908136/+subscriptions



More information about the foundations-bugs mailing list