Call for Adoption: SEARCH method

Looking again over the spec, I see that it specifically states in section 2 the response is NOT cacheable:

 The response to a SEARCH request is not cacheable.  It ought to be
   noted, however, that because SEARCH requests are safe and idempotent,
   responses to a SEARCH MUST NOT invalidate previously cached responses
   to other requests directed at the same effective request URI.

Right after that, the draft states it supports conditional SEARCH, IF-Match etc.

Am I correct that this means that a server can return an ETAG with a response, and the client can technically cache that along with the ETAG and use the ETAG in a subsequent conditional SEARCH?

Glenn Block (he/him/his) | M365 Core Ecosystem | @gblock <> | Principal PM Lead | Schedule with me!<>

Received on Thursday, 5 November 2020 16:30:47 UTC