You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Graham Leggett <mi...@sharp.fm> on 2016/07/27 13:25:58 UTC

Caching PROPFIND

Hi all,

According to https://tools.ietf.org/html/rfc7234#section-2, it says the following:

"However, it is also possible to cache [...] responses to methods other than GET if the method's definition allows such caching and defines something suitable for use as a cache key."

Would it therefore be reasonable to teach mod_cache how to cache methods other than GET in some kind of configurable fashion, with PROPFIND being the obvious example?

Regards,
Graham
—


Re: Caching PROPFIND

Posted by Stefan Eissing <st...@greenbytes.de>.
Just chatted with Julian Reschke shortly about this. It's certainly reasonable to do what you describe. It might not be trivial to get it right, depending on request body, content-location response header and exposed etag/last-mod/cache-control headers. The question is where to re-validate against, for example.

-Stefan

> Am 27.07.2016 um 15:25 schrieb Graham Leggett <mi...@sharp.fm>:
> 
> Hi all,
> 
> According to https://tools.ietf.org/html/rfc7234#section-2, it says the following:
> 
> "However, it is also possible to cache [...] responses to methods other than GET if the method's definition allows such caching and defines something suitable for use as a cache key."
> 
> Would it therefore be reasonable to teach mod_cache how to cache methods other than GET in some kind of configurable fashion, with PROPFIND being the obvious example?
> 
> Regards,
> Graham
> —
>