From: Avery Pennarun <apenwarr@gmail.com>
Date: Tue, 27 Oct 2009 16:53:39 GMT
Subject: Re: From 200 to 404 to 407.
Message-ID: <32541b130910270953w6bd35ddctd471e682830b8f62@mail.gmail.com>
In-Reply-To: <82fd2c5d0910270318wc30bc44tfd3362933d3f62cf@mail.gmail.com>

On Tue, Oct 27, 2009 at 6:18 AM, Peter Odéus <peter.odeus@gmail.com> wrote:
> Doing a "git clone..." using authenticated proxy (set in $http_proxy):
>
> Upon initial success (HTTP 200) and receiving a single HTTP 404 (not
> found), every GET after that renders a HTTP 407 (Proxy authentication
> required).
>
> curl -I "url_giving_http_407" comes out just fine as a HTTP 200.

The easiest way to track this down is to log it using ethereal, and
compare the http session dumps.  There may be differences in headers
or something that git is providing vs. the command-line curl.

If you don't know how to analyze http dumps, then just log them to a
file using tcpdump's -w option and email them to me, and I'll take a
look.  (I probably won't fix the bug in git, but I can at least tell
you what/if the bug is :))  Please don't send the binary dumpfiles to
the mailing list, though.

Have fun,

Avery