Comment 9 for bug 1847084

@davidgar15

This is intended. The idea is that the user sets what HTTP proxy is available for use, but Juju only populates the JUJU_HTTPS_PROXY env var. Then the charm can decide if it needs to use the proxy or not. e.g. if the communication is for one unit to hit an HTTP API on another unit it doesn't need the proxy. However, if the unit it trying to reach the public internet it probably does use it. This is why we have the split in different proxy variables.

When Juju was only setting the HTTPS_PROXY env var it became a mess because then there was a ton of NO_PROXY setup that needed working so that other aspects would operate correctly.