Re: Communicating Warning Information in HTTP APIs

I have wanted Warning headers on a few occasions, sometimes for metadata that doesn't make sense inside a resource representation (e.g., use of a deprecated media type or some aspect of the request being ignored, such as an unknown URL query parameter or specification of a protected field in the payload) and sometimes for communicating with a client independent of any particular resource altogether (e.g., approaching a rate limit or session expiration).

There were also more use cases in the past, but I feel that improvements such as Preference and Preference-Applied have satisfactorily addressed them.

Received on Wednesday, 20 November 2019 15:38:46 UTC