The Deprecation HTTP Header Field
draft-dalal-deprecation-header-03
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Sanjay Dalal , Erik Wilde | ||
| Last updated | 2020-12-15 (latest revision 2020-06-13) | ||
| Replaced by | draft-ietf-httpapi-deprecation-header | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-httpapi-deprecation-header | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-dalal-deprecation-header-03.txt
Abstract
The HTTP Deprecation response header field can be used to signal to consumers of a URI-identified resource that the resource has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides additional context for the deprecation, and possibly ways in which clients can find a replacement for the deprecated resource.
Authors
Sanjay Dalal
(sanjay.dalal@cal.berkeley.edu)
Erik Wilde
(erik.wilde@dret.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)