IP addresses mismatch in
--noproxy and related env variable (in 7.86.0)
I did this
I expected the following
both curls downloading the file and not reaching out to the proxy, but if "127.0.0.1" is not the last part of the string ... it will not work
[curl -V output]
This came with 7.86.0 and showed up in a CI pipline testing multiple "modern distros". It came with "alpine:edge" and "archlinux:latest" at the same time. Both switched to that new curl yesterday.
docker containers of "alpine:edge" and "archlinux:latest" ... or Linux with the latest curl
The text was updated successfully, but these errors were encountered:
I would say that is a regression which might even call for a new release rather soon. Nice to see there is a workaround. But if you ever had the honors to having to work with proxies and related env variables, you will know how horrible all of that is.
The variables are used by many tools and they all have their own implementation on dealing with them. While curl is an important player in that game it is not the only one. Just think multiple versions of curl all hoping to use the same
In my example i pointed it out via cmdline
Thanks for that quick fix but there is more to it. I tried to make that workaround get a whole complex pipeline green where proxies are needed for several things. The IP just being one of several essential parts of
And again it tries to go via that proxy where it should not.
arch was not notfied so let my try with a ping @eworm-de
alpine is also affected @ncopa
opensuse tumbleweed is now also affected by both issues, also trying a ping @pmgdeb
debian bookworm is affected ... ping @samueloph
fedora and gentoo have backported the patches for this one and #9821
Sorry for the direct maintainer SPAM, but i think this one is important and easy to miss. So i did dig out some names of distros and people to notify all at once, not following individual workflows. Please do not ask me to open a bug, i might do that for debian but not the rest.