RE: Caching returns from POST

One of the development guys would be able to answer the specifics of what
Squid can do, but that answer will almost certainly be 'no'. POST involves a
request body, which Squid is totally unequipped to deal with, AFAIK. What
you're talking about would also break a lot of other things.

HTTP 1.1 says that POST is cacheable with the approprate Cache-Control:
headers, but I don't know of a proxy that will actually cache it (somebody
prove me wrong?)

You may have better luck writing a POST -> GET munger that can sit on the
Verity server, wait for GET requests from the cache, POST to Verity, and
then serve the appropriate XML response. That way, you have complete control
over the object headers. I've done something similar (adding IMS
functionality to a cgi script) and it really isn't too bad.

Have fun,

> -----Original Message-----
> From: Mike Batchelor [mailto:mbatchelor@citysearch.com]
> Sent: Wednesday, June 02, 1999 10:53 AM
> To: squid-users@ircache.net
> Subject: Caching returns from POST
>
>
> Is it possible to cache returns from a POST request with Squid?
> Can I get an example of how to do this?
>
> I also want to pin the returns in the cache for a set period
> of time - 12 to
> 24 hours - regardless of any cache-control headers (or lack
> thereof) that
> are returned by the origin server.
>
> Background: we use the Verity search engine on our web site.
> We want to put
> squid in between the front web servers, and the Verity search
> engine. The
> web servers accept visitor searches using HTML forms, pass
> the form data
> into a web server plugin, which formulates a request via HTTP
> POST to the
> Verity search engine. Verity responds with a XML document,
> which is further
> processed by our templating system, ads are inserted, and
> finally it is
> returned as a HTML document to the visitor. We have identified a huge
> potential for a search performance boost if we can cache the
> returns for
> popular search terms with squid sitting in between the web
> servers and the
> Verity engine.
>
> Squid would be configured as a reverse-proxy accelerator in
> this situation.
> The web servers would be configured to make the Verity POST
> requests to
> Squid, which would (ideally) already have the response in the cache.
>
> Any help is greatly appreciated.
>
>
Received on Tue Jun 01 1999 - 19:21:35 MDT