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

Communicating Warning Information in HTTP APIs

From: André Cedik <andre.cedik@googlemail.com>
Date: Tue, 5 Nov 2019 19:58:36 +0100
Message-ID: <CAEQcYZgHNcOv5tMv+E4oRJs8rpSugEPcT=NaZAM53v=0nkotcQ@mail.gmail.com>
To: ietf-http-wg@w3.org
Hey everyone,

Erik Wilde submitted an I-D on Monday - using the subject of this mail as
the title (see https://datatracker.ietf.org/doc/draft-cedik-http-warning/)
- that he and I wrote. It is our goal "to allow HTTP providers to have a
standardized way of communicating to their consumers that while the
response can be considered to be a non-failure, there is some warning
information available that they might want to take into account".

Shortly after we submitted the draft Julian Reschke notified us (see
https://github.com/dret/I-D/issues/125) that the Warning header is bound to
be removed with the next spec (draft-ietf-httpbis-cache). Which is very
unfortunate for the I-D since we wanted to use it for indicating that the
client would find additional information within the response body.

Since there is currently no other way of conveying this to an http client
(that we know of), we'd really like to get feedback if this is a use case
for which you would be willing to keep the Warning header or if there is
another way to make something like this possible.

André Cedik
Received on Wednesday, 6 November 2019 03:18:40 UTC

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