[Bug 203861] 'fetch' command fails when HTTP_PROXY env. variable is set, and there is a http->https redirect

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sun Oct 18 23:23:19 UTC 2015


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203861

mvharding at gmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|Affects Only Me             |Affects Some People

--- Comment #1 from mvharding at gmail.com ---
Regular fetch works fine (I have a squid proxy on 192.168.0.2 on my local
network):

$ fetch
http://pypi.python.org/packages/source/c/cryptography/cryptography-1.0.2.tar.gz
fetch
http://pypi.python.org/packages/source/c/cryptography/cryptography-1.0.2.tar.gz
cryptography-1.0.2.tar.gz                     100% of  325 kB  822 kBps 00m01s

Setting a proxy does not work:

$ HTTP_PROXY=http://192.168.0.2 fetch
http://pypi.python.org/packages/source/c/cryptography/cryptography-1.0.2.tar.gz
HTTP_PROXY=http://192.168.0.2 fetch
http://pypi.python.org/packages/source/c/cryptography/cryptography-1.0.2.tar.gz
fetch:
http://pypi.python.org/packages/source/c/cryptography/cryptography-1.0.2.tar.gz:
Not Found

This seems (to me) to affect all pypi packages, as there is a 301 redirect from
http to https.  If I try to get the 'https' stuff directly, it works fine.

$ HTTP_PROXY=http://192.168.0.2 fetch
https://pypi.python.org/packages/source/c\
/cryptography/cryptography-1.0.2.tar.gz
HTTP_PROXY=http://192.168.0.2 fetch
https://pypi.python.org/packages/source/c/c\
ryptography/cryptography-1.0.2.tar.gz
cryptography-1.0.2.tar.gz                     100% of  325 kB  825 kBps 00m00s

This could, I guess, be worked around by changing the base for the pypi fetches
to 'https'.  Right, now, most Python package fetches fail unless I disable the
proxy.

I did some runs with '-vvv' but and can see the 301 redirect (I can paste the
whole session here, but it's easy to recreate...).

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list