Re: Problem with git fetch over http://

From: Junio C Hamano <gitster@pobox.com>
Date: Apr 25, 2008, 21:24 UTC
Message-ID: <7v3ap9pr07.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <63F7B390-32D1-458A-8ED9-D5AC62F46745@newartisans.com>

John Wiegley <johnw@newartisans.com> writes:

Show 18 quoted lines

> Hello, I'm using the Builtbot to pull sources from a Git repository,
> and have found that the Buildbot's Git step always uses git-fetch -- a
> detail of Buildbot which I currently have little control over.
>
> This is no problem if the git:// protocol is used, but using fetch
> with http:// doesn't work.  This has been mentioned elsewhere:
>
>   http://lists.berlios.de/pipermail/bitbake-dev/2007-November/000765.html
>
> Here's a quick example of what I mean:
>
>   cd /tmp ; mkdir foo ; cd foo ; git init
>
>   git fetch git://newartisans.com/ledger.git	# works fine
>
>   cd /tmp ; rm -fr foo ; mkdir foo ; cd foo ; git init
>
>   git fetch http://newartisans.com/git/ledger.git  # fails

Is this related to this independent observation?

$ wget http://newartisans.com/git/ledger.git
--14:23:54--  http://newartisans.com/git/ledger.git
           => `ledger.git'
Resolving newartisans.com... 208.70.150.153
Connecting to newartisans.com|208.70.150.153|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://git.newartisans.com//ledger.git [following]
--14:23:55--  http://git.newartisans.com//ledger.git
           => `ledger.git'
Resolving git.newartisans.com... 208.70.150.153
Connecting to git.newartisans.com|208.70.150.153|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: http://git.newartisans.com/ledger.git/ [following]
--14:23:55--  http://git.newartisans.com/ledger.git/
           => `index.html'
Connecting to git.newartisans.com|208.70.150.153|:80... connected.
HTTP request sent, awaiting response... 403 Forbidden
14:23:55 ERROR 403: Forbidden.