Communicating Warning Information in HTTP APIs
draft-cedik-http-warning-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | André Cedik , Erik Wilde | ||
| Last updated | 2021-03-27 (Latest revision 2020-09-23) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document defines a new HTTP field Content-Warning and a standard response format for representing warning information in HTTP APIs. Note to Readers This draft should be discussed on the rfc-interest mailing list (<https://lists.w3.org/Archives/Public/ietf-http-wg/>). Online access to all versions and files is available on GitHub (<https://github.com/dret/I-D/tree/master/http-warning>).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)