Caching POSTs

[Christian Kratzer]

Hi,

On Fri, 6 Nov 2009, rtshilston at gmail.com wrote:

> I thoroughly disagree with this use of HTTP.  If a request makes an impact on a system, then it should use POST (eg login, pay, delete).  However, if it has no write-behaviour (other than, perhaps, logging) then it must be GET.

This kind of behaviour seems quite frequent in the context of webservices which are often POST only.

This is of course not the classic use case of varnish between client browsers and webservers.

Greetings
Christian Kratzer
CK Software GmbH


>
> If you follow this, then varnish will work fine.
>
> Can you explain more about your actions?   If you're using a processing server to build reports then GET should be fine.
>
> Rtsh
>
> -- Sent from my Palm Pr?
> Rob Ayres wrote:
>
> 2009/11/6 Tollef Fog Heen <tfheen at redpill-linpro.com>
>
> ]] Rob Ayres
>
>
>
> | I want to cache POSTs but can't get varnish to do it, is it possible? If it
>
> | makes it any easier, all requests through this cache will be of POST type.
>
>
>
> No, you can't cache POSTs.  It doesn't make any sense to do so.
>
>
> We have a processing server and a database server. The processing server makes its requests to the database server by means of a POST. There is enough duplication in the POST requests to have made it worth having a caching server between the two.
>
>
>
>
>

-- 
Christian Kratzer                      CK Software GmbH
Email:   ck at cksoft.de                  Schwarzwaldstr. 31
Phone:   +49 7452 889 135              D-71131 Jettingen
Fax:     +49 7452 889 136              HRB 245288, Amtsgericht Stuttgart
Web:     http://www.cksoft.de/         Geschaeftsfuehrer: Christian Kratzer