Comment 4 for bug 2025978

The thing is setting http-proxy globally in one model has side effects. That's why juju-http-proxy was born to give a more granular control over what traffic should be proxied or not.

The legacy charm had http-proxy and https-proxy in the charm config itself so it was okay. And the new charm has http_proxy and https_proxy but I don't see an implementation in the charm to leverage those values at all.

So the issue here is there is no way to use proxy if we use juju-http-proxy instead of the legacy model global http-proxy which is full of side-effect.