Re: Call for Adoption: SEARCH method

The draft says "The response to a SEARCH request is not cacheable.".  Why
is that?  Semantically, it seems that caching keyed by the request body
should behave correctly.

RFC 7234 says "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.".

Without support for caching, I don't have any reason to prefer this method
over POST.  With support for caching, this would have been very useful in

On Tue, Nov 3, 2020 at 8:10 PM Mark Nottingham <> wrote:

> As discussed in the October 202 Interim, this is a Call for Adoption for
> the HTTP SEARCH method draft:
> Please indicate whether you support adoption in response to this e-mail;
> information about intent to implement (or use) it is also useful.
> The Call for Adoption will end on 18 November 2020.
> Cheers,
> Mark and Tommy

Received on Thursday, 5 November 2020 16:45:28 UTC