Re: [EXTERNAL] Call for Adoption: SEARCH method

I support adoption.

This is great to see. I've been a fan of this method since I first learned about it years ago.

One place I think this would be valuable is for GraphQL usage. One of the common critiques of GraphQL is that the HTTP caching story is very limited, as by default all requests are via POST.

The GraphQL HTTP w/g has done some work to specify how different methods can be used but you are still limited by the fact that the query is sent via the query string.

Reading through the draft, it says that responses are not cachable, but it sounds like there is "some" client caching through usage of ETAGs and conditional SEARCH requests.

Why not allow support cachable responses? It would be great if there was a way to leverage caches fully.


Glenn Block (he/him/his) | M365 Core Ecosystem | @gblock <> | Principal PM Lead | Schedule with me!<>
From: Mark Nottingham <>
Sent: Tuesday, November 3, 2020 5:07 PM
To: HTTP Working Group <>
Cc: Tommy Pauly <>
Subject: [EXTERNAL] Call for Adoption: SEARCH method

As discussed in the October 202 Interim, this is a Call for Adoption for the HTTP SEARCH method draft:;;sdata=RzTJaZTWHxqmR2zgipC4%2FrIdNQI5kGd73RDTii%2Ba8Ng%3D&amp;reserved=0

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.


Mark and Tommy

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