W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2020

Re: Call for Adoption: SEARCH method

From: Mark Nottingham <mnot@mnot.net>
Date: Sat, 7 Nov 2020 10:23:33 +1100
Cc: James M Snell <jasnell@gmail.com>, Glenn Block <Glenn.Block@microsoft.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <34F73C71-1AEC-40C2-A930-A797DB619057@mnot.net>
To: Ben Schwartz <bemasc@google.com>
On 7 Nov 2020, at 8:02 am, Ben Schwartz <bemasc@google.com> wrote:
> 
> James, according to RFC 7234 Section 3:
>    A cache MUST NOT store a response to any request, unless:
>    o  The request method is understood by the cache and defined as being
>       cacheable
> 
> I think it follows that you do not need to declare this method non-cacheable; you can declare it cacheable when keyed by exact match on the body.  Existing intermediaries will not cache it anyway, since they do not understand the method.

I'm hoping we can do better than that. E.g., the request media type can define how it can be canonicalised into input for the cache key.. Or a response header might describe how to do it, a la Variant.

But that's getting ahead of the CfA...

Cheers,

--
Mark Nottingham   https://www.mnot.net/
Received on Friday, 6 November 2020 23:23:53 UTC

This archive was generated by hypermail 2.4.0 : Friday, 6 November 2020 23:23:54 UTC