Bug 1241045

Description of problem:
When executing osc exec, the proxy configured with HTTP_PROXY is ignored. Other commands such as osc logs -f ... are respecting HTTP_PROXY and are working fine.

Version-Release number of selected component (if applicable):

Reported with osc version 0.5.2.2 running on windows 7 to an OSE 3.0 beta 4 installation.

Reproduced with oc v3.0.0.0-25-g235b0e7 on Linux to an OSE 3.0 GA.

How reproducible:
Always

Steps to Reproduce:
1. Have an oc client system without direct connectivity to OSE except via an HTTP proxy:
   export HTTP_PROXY=<proxy_url>
2. Attempt an "oc exec" command

Actual results:
The command "osc exec -p xyz-6-aabv1  -- ls" fails with:

 report: error: Error sending request: Get https://master:8443/api/v1beta3/namespaces/test/pods/xyz-6-aabv1/exec?command=ls&container=xyz&stderr=true&stdout=true: dial tcp X.X.X.X:8443: ConnectEx tcp: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

 reproducer: error: Error sending request: Get https://master:8443/api/v1/namespaces/test/pods/xyz-6-aabv1/exec?command=ls&container=xyz&stderr=true&stdout=true: dial tcp X.X.X.X:8443: connection refused

Expected results:
"oc exec" would work over a proxy.

Also, it should work when the proxy requires authentication.

Additional info:
Configuring http_proxy (lowercase) makes no difference.