git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Problem with git fetch over http://

From
Mike Hommey <mh@glandium.org>
Date
Apr 25, 2008, 21:34 UTC
Message-ID
<20080425213411.GA25964@glandium.org>
In-Reply-To
<7v3ap9pr07.fsf@gitster.siamese.dyndns.org>
On Fri, Apr 25, 2008 at 02:24:24PM -0700, Junio C Hamano wrote:
Show 41 quoted lines
> John Wiegley <johnw@newartisans.com> writes:
> 
> > 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.
Probably, but even then, it also doesn't have a HEAD.
Mike
Previous: Junio C HamanoNext: Daniel Barkalow
Message 3 of 6 in “Problem with git fetch over http://”
  1. John WiegleyApr 25, 2008
  2. Junio C HamanoApr 25, 2008
  3. Mike HommeyApr 25, 2008
  4. Daniel BarkalowApr 25, 2008
  5. Junio C HamanoApr 25, 2008
  6. Daniel BarkalowApr 25, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.