Need support for https_proxy and no_proxy

[Christian Reis]

We re-implemented support for proxies with bug 1384464, but in the merge review it became clear that we are lucking out today because https_proxy is not supported. Furthermore, we don't allow the admin to specify a no_proxy field at all, which we should if the environment requires something special.

[Julian Edwards (julian-edwards)]

Nobody has ever asked for this and I've never seen anyone using a separate SSL proxy. Is it really required for "next" ?

[Gavin Panella (allenap)]

These overlap a bit with Julian's point, but here goes anyway:

* No one has asked for separate HTTP and HTTPS proxy settings, so we
  only offer a single setting for both.

* Internally, MAAS passes around separate HTTP and HTTPS proxy settings,
  but that's an implementation detail. At present they always have the
  same value.

* It's common to use the same proxy for both HTTP and HTTPS. Browsers
  and other HTTPS clients use the CONNECT verb when accessing HTTPS
  sites via a proxy.

* no_proxy is calculated and set automatically by _run_import so that
  the region is not accessed via any configured proxy. If we need to
  avoid proxies elsewhere we should try the same approach: to calculate
  the setting and set it without user intervention. No one has asked for
  a user-configurable setting for this.

I'm not sure if that makes this Invalid or Won't Fix.

[Serge Hallyn (serge-hallyn)]

is no_proxy still not supported? not seeing it as an option in the web ui.

[Adam Collard (adam-collard)]

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.

MAAS Team