On 05/30/2008 11:39 AM, rahul wrote:
[..]
| >>The patch actually works, you can call;
| >>
| >>PURGE /foo HTTP/1.1
| >>Host: example.org
| >>Accept: foo/bar
| >>
[..]
| the PURGE request. So sending a PURGE request to 127.0.0.1:8080 with the
| caching
| virtual host being 'cachehost' will look like:
|
| PURGE http://cachehost/someuri HTTP/1.1
| ....
Isn't it better to do it as a uri - say - /cache-control - hosted on the proxy?
so the above would look like
POST /cache-control?purge
http://cachehost/someuri1
http://cachehost/someuri2
http://cachehost/someuri3
the advantage is that standard http clients like wget can be used to purge a
number of URLs (or based on wild cards) and it does not use any non-rfc methods.
If implemented as a handler it would also give you ACL/auth for free. OTOH it
gets
more difficult to implement the actual deleting from the cache. Furthermore you
cannot delete specific variants.
Regards
Rüdiger
