> Right now the spec does not define the result of this query as cacheable. It's not completely clear why
That was the unique selling point of SEARCH over POST though.
How about using the Range header with a custom value domain instead?
That was the unique selling point of SEARCH over POST though.
How about using the Range header with a custom value domain instead?
Search is idempotent in the sense that it doesn't change anything on the server, other than mutating caches (which should be idempotent).