Handle no_proxy configuration setting

[Andreas Hasenack]

A no_proxy configuration setting would accept a list of domains, comma separated, for which no proxy should be used. It's honored by curl, and there is also an env variable with the same name ("no_proxy") that has the same meaning and syntax.

For example, using just env vars and smart (which also uses curl: https://pastebin.canonical.com/51226/

[🤖 Landscape Builder (landscape-builder)]

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

Landscape Team

[Michael Croft-White (mikec-w)]

No update in > 5 years.

[Philipp Neuhaus (philippunims)]

I encounter the same problem:

On some of my VMs a proxy is needed to access the internet.

But it must not needed to access our on-prem-landscape.

Calling "landscape-config" to register the VM ends in the script asking for Proxy. It automatically fills in the system environments value - no possibility to deny the proxy.

Even calling the script with "--http_proxy="" --https_proxy="" " does not work...