5 ms·
> 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
by dejj 5y ago
> 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?
- compressedgas 5y agoI thought the point was that SEARCH would be idempotent whereas POST is not.
- pii 5y agoSearching already isn't idempotent
- remram 5y agoidempotent != immutable Search is idempotent in the sense that it doesn't change anything on the server, other than mutating caches (which should be idempotent).
- naniwaduni 5y agoPretty sure nobody cares about ensuring that e.g. a proxy knows that nothing will go wrong if it issues a search twice. It's the reverse direction that matters.
- remram 5y agoYes, this is why search is idempotent
- pii 5y agoOh TIL. Thanks