Re: How to express no matching results in HTTP SEARH method?

That certainly has been the intent to this point, yes, and it's what
I'd like to see. Anything else can be done as a separate piece of

For instance, for something like a "don't repeat this search" for
N-seconds, one can make use of 425 Too Early responses, or 429 Too
Many Requests responses with a Retry-After header. There's no reason
that existing mechanisms would not work, or to think that something
specific to SEARCH needs to be hashed out.

On Wed, Nov 4, 2020 at 6:22 AM Julian Reschke <> wrote:
> My understanding is that we essentially want to define something that is
> the same as POST, with the additional property of being safe by
> definition. Nothing more specific than that.
> Best regards, Julian

Received on Wednesday, 4 November 2020 14:36:10 UTC