3 ms·
Can be useful for some APIs. The use-case 4.2 with both Content-Location and Location feels weird to me. Not sure you would want multiple urls with different m
by cryptonym 2y ago
Can be useful for some APIs.
The use-case 4.2 with both Content-Location and Location feels weird to me. Not sure you would want multiple urls with different meanings. Isn't it harder to keep it idempotent if we are generating URLs for request and result? Not sure Location is generally meaningful in 200... that may impact other RFC.
Could be interesting to see a sample where query is created but result will be available later. That's probably just the 303 See Other with a Retry-After?
- cryptonector 2y agoContent-Location refers to a specific response to the given query. Location refers to a URI that denotes the given query. It's a bit strange, since I don't think it's likely that a server will want to persist any particular response to a query for very long. But it's not unreasonable to support that.