Handle no_proxy configuration setting
Bug #827997 reported by
Andreas Hasenack
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Landscape Client |
Triaged
|
Medium
|
Unassigned | ||
| landscape-client (Juju Charms Collection) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
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:/
| Changed in landscape-client: | |
| importance: | Undecided → Medium |
Revision history for this message
| 🤖 Landscape Builder (landscape-builder) wrote | #1 |
| Changed in landscape-client: | |
| status: | New → Invalid |
| Changed in landscape-client: | |
| status: | Invalid → Triaged |
| tags: | added: proxy theme-proxy |
| Changed in landscape-client (Juju Charms Collection): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
To post a comment you must log in.
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