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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux