RFC 9745: The Deprecation HTTP Response Header Field
In plain English — editorial summary, not part of the RFC
The Deprecation HTTP response header field is used to signal to consumers of a resource (identified by a URI) that the resource will be or has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides further information about planned or existing deprecation. It may also provide ways in which client application developers can best manage deprecation.
Document record
- Document ID
- RFC9745
- Published
- March 2025
- Authors
- S. Dalal; E. Wilde
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9875HTTP Cache GroupsCurrent
October 2025
- RFC 9484Proxying IP in HTTPCurrent
October 2023
- RFC 10008The HTTP QUERY MethodCurrent
June 2026
- RFC 9457Problem Details for HTTP APIsCurrent
July 2023
- RFC 9440Client-Cert HTTP Header FieldCurrent
July 2023
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9297HTTP Datagrams and the Capsule ProtocolCurrent
August 2022
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?