Rudder

https://github.com/Normation/rudder-techniques/pull/466

Jon, could you review this ? thank you

I don't think simply removing the proxy option is a good idea.

The reason we introduced this is explained in #3383, but let me summarize: often the http_proxy environment variable is defined on servers, to enable tools to "get out" on the internet (for example to hit package repositories, download software, etc...).

However, these proxies are usually only configured to route HTTP traffic outside of the corporate network. But Rudder's HTTP requests almost always target a HTTP server inside the network, possibly in some sort of network-control-area, that is unknown (or deliberately forbidden) by the proxy server. This is why we currently force curl to use no proxy.

I understand that this Pull Request is based on the fact that the "--proxy" option doesn't exist on the version of curl for Windows you're using, but I'd like to be sure this is the best approach to fixing this. What are our other options?

• Are we just using a really old version of curl, and therefore upgrading would be enough?
• How does curl use/not use a proxy if the --proxy option is not available? It must be able to, this is basic HTTP-fu.
• Is there an equivalent mechanism in Windows to the http_proxy environment variable in UNIX that we could/should use?

Applied in changeset policy-templates:commit:f614de222c16379e343ff8f2f2feeb9a45cf5617.

This bug has been fixed in Rudder 2.10.7 and 2.11.4, which were released today.

• Announcement 2.10 2.11
• Changelog 2.10 2.11
• Download information: https://www.rudder-project.org/site/get-rudder/downloads/