Re: From 200 to 404 to 407.

From: Peter Odéus <peter.odeus@gmail.com>
Date: Oct 28, 2009, 16:10 UTC
Message-ID: <loom.20091028T170227-957@post.gmane.org>
In-Reply-To: <32541b130910280850t5b4baa91p90b31b4c1c467e94@mail.gmail.com>

Avery Pennarun <apenwarr <at> gmail.com> writes:

> 
> On Wed, Oct 28, 2009 at 4:38 AM, Peter Odéus <peter.odeus <at> gmail.com>

wrote:

> > * Re-using existing connection! (#0) with host proxyserver.acme.com
> > * Connected to proxyserver.acme.com (192.71.145.9) port 8080
> > > GET
>

http://gitrepo.outside.com/git/gitrepo.git/objects/6b/132a9e81161e58812902d7f735 a38bf5ee1583 HTTP/1.1

Show 18 quoted lines

> > Proxy-Authorization: Basic cmQva3F3Zzc2MjptYW1tYW1pYQ==
> > User-Agent: git/1.6.5.2
> > Host: gitrepo.outside.com
> > Accept: */*
> >
> > * The requested URL returned error: 404
> 
> So this git object didn't exist, apparently.  Can you confirm that the
> object shouldn't be there?  (on the server: git cat-file -p
> 6b132a9e81161e58812902d7f735a38bf5ee1583)  Does git-fsck report
> anything weird on the server repository?
> 
> > * Closing connection #0
> > * Couldn't find host gitrepo.outside.com in the .netrc file, using defaults
> > * About to connect() to proxyserver.acme.com port 8080
> > *   Trying 192.71.145.9... * connected
> > * Connected to proxyserver.acme.com (192.71.145.9) port 8080
> > > GET http://gitrepo.outside.com/git/gitrepo.git/objects/info/http-

alternates HTTP/1.1

Show 31 quoted lines

> > User-Agent: git/1.6.5.2
> > Host: gitrepo.outside.com
> > Accept: */*
> > Pragma: no-cache
> >
> > < HTTP/1.1 407 Proxy Authentication Required ( The ISA Server requires
> > authorization to fulfill the request. Access to the Web Proxy service
> > is denied.  )
> 
> This error seems to happen because the Proxy-Authorization line was
> not included in this request like it was included in prior ones.
> Probably the authorization key was forgotten when the first connection
> closed.  If there hadn't been a 404, the connection wouldn't have
> closed and this wouldn't have happened, which is presumably why you
> haven't seen this problem before.
> 
> This is where my expertise ends, since I've never messed with either
> libcurl or git's usage of it.  I couldn't tell you if this is a
> libcurl bug or a git bug.  (Proxies are relatively rare nowadays, so
> this code path is likely to be rarely tested.)
> 
> Hopefully someone else on the list can assist.
> 
> ** WARNING: the username/password sent in the Proxy-Authorization line
> is not encrypted and you've posted a trace of it to a public mailing
> list.  You need to change your password immediately. **
> 
> Good luck,
> 
> Avery
>

If you wouldn't have posted the base64-encoded password it would have never hit the gmane list ;-)

Don't worry about it, because I tried to submit the console output myself all day. But to no avail.

Is it enough to replace greater-than-signs to something else, btw?

Anyway. Behind these corporate walls, the proxy is a reality to deal with, so hopefully someone else can bring us closer to a solutiuon.

Thanks for your input.

:D

/Peter