cmd/juju: no support for proxies

[Dave Cheney]

Reported by client in the field.

A client using AWS behind a restritive (http/https only firewall) was not able to use their environment via the juju gui once bootstrapped.

Juju should transparently support http (using CONNECT) or socks4/5 proxies if defined in the environment.

[John A Meinel (jameinel)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2013-12-02 14:11, Dave Cheney wrote:
> Public bug reported:
>
> Reported by client in the field.
>
> A client using AWS behind a restritive (http/https only firewall)
> was not able to use their environment via the juju gui once
> bootstrapped.
>
> Juju should transparently support http (using CONNECT) or socks4/5
> proxies if defined in the environment.
>
> ** Affects: juju-core Importance: Undecided Status: New
>

If you "export http_proxy=XYZ" I'm pretty sure we use it. (The go
internal http.Client stuff defaults to ProxyFromEnvironment, which I
think we're using.)

I haven't explicitly tested this myself, though.

 importance high
 status triaged

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlKchYUACgkQJdeBCYSNAAMdFQCgj+rsjsbatvbsyY8wjPgoOZwo
BVIAn3JrtOo8Hmgyg/TjfKXPhUzhTb+1
=/lMi
-----END PGP SIGNATURE-----