Re: [RFC 2/2] Add Git-aware CGI for Git-aware smart HTTP transport

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Aug 4, 2008, 10:08 UTC
Message-ID: <alpine.DEB.1.00.0808041208060.9611@pacific.mpi-cbg.de.mpi-cbg.de>
In-Reply-To: <4896D19C.6040704@dawes.za.net>

Hi,

On Mon, 4 Aug 2008, Rogan Dawes wrote:

Show 29 quoted lines

> Shawn O. Pearce wrote:
> 
> > Perhaps the smart server detection is something like:
> > 
> >  Smart Server Detection
> >  ----------------------
> > 
> >  To detect a smart (Git-aware) server a client sends an
> >  empty POST request to info/refs; if a 200 OK response is
> >  received with the proper content type then the server can
> >  be assumed to be Git-aware, and the result contains the
> >  current info/refs data for that repository.
> > 
> > C: POST /repository.git/info/refs HTTP/1.0
> > C: Content-Length: 0
> > 
> > S: HTTP/1.0 200 OK
> > S: Content-Type: application/x-git-refs
> > S:
> > S:95dcfa3633004da0049d3d0fa03f80589cbcaf31	refs/heads/maint
> > 
> > Then clients should just attempt this POST first before issuing
> > a GET info/refs.  Non Git-aware servers will issue an error code,
> > and the client can retry with a standard GET request, and assume
> > the server isn't a newer style.
> > 
> 
> I don't understand why you would want to keep the commands in the URL 
> when you are doing a POST?

Caching.

Hth, Dscho