RFC 9209: The Proxy-Status HTTP Response Header Field
In plain English — editorial summary, not part of the RFC
This document defines the Proxy-Status HTTP response field to convey the details of an intermediary's response handling, including generated errors.
Document record
- Document ID
- RFC9209
- Published
- June 2022
- Authors
- M. Nottingham; P. Sikora
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 22
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9298Proxying UDP in HTTPUpdated
August 2022
- RFC 9484Proxying IP in HTTPCurrent
October 2023
- RFC 8828WebRTC IP Address Handling RequirementsCurrent
January 2021
- RFC 9458Oblivious HTTPCurrent
January 2024
- RFC 9666Area Proxy for IS-ISCurrent
October 2024
- RFC 8302Transparent Interconnection of Lots of Links (TRILL): ARP and Neighbor Discovery (ND) OptimizationCurrent
January 2018
- RFC 8165Design Considerations for Metadata InsertionCurrent
May 2017
- RFC 8041Use Cases and Operational Experience with Multipath TCPCurrent
January 2017
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?