From owner-freebsd-bugs@freebsd.org Sun Oct 18 23:23:19 2015 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 616BAA185DC for ; Sun, 18 Oct 2015 23:23:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 33A8F2B for ; Sun, 18 Oct 2015 23:23:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9INNJns050163 for ; Sun, 18 Oct 2015 23:23:19 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 203861] 'fetch' command fails when HTTP_PROXY env. variable is set, and there is a http->https redirect Date: Sun, 18 Oct 2015 23:23:19 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 10.2-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: mvharding@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_severity Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Oct 2015 23:23:19 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203861 mvharding@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Affects Only Me |Affects Some People --- Comment #1 from mvharding@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.