From: Rogan Dawes <lists@dawes.za.net>
Date: Mon, 04 Aug 2008 10:14:01 GMT
Subject: Re: [RFC 2/2] Add Git-aware CGI for Git-aware smart HTTP transport
Message-ID: <4896D669.30402@dawes.za.net>
In-Reply-To: <alpine.DEB.1.00.0808041208060.9611@pacific.mpi-cbg.de.mpi-cbg.de>

Johannes Schindelin wrote:
> Hi,
> 
> On Mon, 4 Aug 2008, Rogan Dawes wrote:
> 
>> I don't understand why you would want to keep the commands in the URL 
>> when you are doing a POST?
> 
> Caching.
> 
> Hth,
> Dscho
> 

If you are expecting something to be cacheable, then should you not be 
using a GET anyway?

Anyway, from RFC 2616:

> 13.10 Invalidation After Updates or Deletions
> 
> ...
> 
> Some HTTP methods MUST cause a cache to invalidate an entity. This is
> either the entity referred to by the Request-URI, or by the Location
 > or Content-Location headers (if present). These methods are:
> 
>       - PUT
>       - DELETE
>       - POST

This doesn't seem negotiable to me.

Unless I am misunderstanding your "Caching" comment to mean "To enable 
caching", as opposed to "To prevent caching"?

Rogan