W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2019

Re: Communicating Warning Information in HTTP APIs

From: <richard.gibson@gmail.com>
Date: Wed, 20 Nov 2019 10:38:32 -0500
Message-ID: <5dd55e03.1c69fb81.c65ac.5874@mx.google.com>
To: ietf-http-wg@w3.org
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

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:15:43 UTC