The Deprecation HTTP Header Field
draft-ietf-httpapi-deprecation-header-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Sanjay Dalal , Erik Wilde | ||
| Last updated | 2024-06-13 (Latest revision 2023-12-11) | ||
| Replaces | draft-dalal-deprecation-header | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Formats | |||
| Reviews |
ARTART Last Call review
(of
-07)
by Julian Reschke
Ready w/nits
GENART Last Call review
(of
-06)
by Robert Sparks
Almost ready
|
||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | In WG Last Call | |
| Associated WG milestone |
|
||
| Document shepherd | (None) | ||
| IESG | IESG state | Expired | |
| Consensus boilerplate | Unknown | ||
| 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
The Deprecation HTTP response header field is used to signal to consumers of a URI-identified resource that the resource will be or has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides additional information about planned or existing deprecation, and possibly ways in which clients can best manage deprecation.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)