Description of problem: TL;DR: The issue is documented at https://github.com/pypa/pip/issues/1805 . The fix is documented at https://github.com/shazow/urllib3/pull/369/files . I have tested applying the fix and it resolves my issue. Please backport it at least to python33 SCL for RHEL7. I'm trying to get the OpenShift 3 Python 3.3 docker image (using python33-python-pip-1.5.6-5.el7.noarch) to do pip installs behind a corporate HTTPS proxy. It bottles out, and I can see using tcpdump that it is attempting to send 'CONNECT' HTTP requests direct to the remote endpoint, not to the proxy. I have tried manually applying the fixes mentioned above to the files under /opt/rh/python33/root/user/lib/python3.3/site-packages/pip/_vendor/requests/packages/urllib3, and find that when I do, the tcpdump is then clean and pip works properly. Version-Release number of selected component (if applicable): python33-python-pip-1.5.6-5.el7.noarch How reproducible: Always Steps to Reproduce: 1. https_proxy=http://<proxy>/ pip --cert=<cert> install --user -r requirements.txt Actual results: Pip bottles out, and I can see using tcpdump that it is attempting to send 'CONNECT' HTTP requests direct to the remote endpoint, not to the proxy. Expected results: Pip installs from requirements.txt as expected.
Sorry to notice so late, but python33-pip is not shipped withing RHSCL product, it is built specifically only for OpenShift, so moving this bug to appropriate product.
Troy, is this backport/rebuild something you can handle? (assuming we do in fact own the python33-pip rpm)? Jim, have you tried the python-34 image instead, or is there a reason you can't use that newer version?
Yes to both. It is something I can handle, have the patch done now. We (OpenShift) do own the python33-pip rpm. Working on it now.
rpm built with fix, python33-python-pip-1.5.6-6.el7, building into image now.
This is now in image openshift3/python-33-rhel7:3.3-40 and newer.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1934