Comment 3 for bug 1749710

> I think it's a fairly widely used and expected behavior.

It is for anything that deals with an HTTP server. I'm a fairly intensive juju user and certainly did not expect "juju status" to use https_proxy.

> Your controller may not be on the same network as your client and you may be running a client behind a corporate firewall in virtually any location.

Likewise, you may have to use an HTTP proxy to access the internet, but you just want to test juju locally and it fails.

Like I said, I guess it's fine if you at least inform the user.