RFC 9532: HTTP Proxy-Status Parameter for Next-Hop Aliases
In plain English — editorial summary, not part of the RFC
This document defines the next-hop-aliases HTTP Proxy-Status Parameter. This parameter carries the list of aliases and canonical names an intermediary received during DNS resolution as part of establishing a connection to the next hop.
Document record
- Document ID
- RFC9532
- Published
- January 2024
- Authors
- T. Pauly
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9530Digest FieldsCurrent
February 2024
- RFC 9538Content Delivery Network Interconnection (CDNI) Delegation Using the Automated Certificate Management EnvironmentCurrent
February 2024
- RFC 9512YAML Media TypeCurrent
February 2024
- RFC 9561Using the Parallel NFS (pNFS) SCSI Layout to Access Non-Volatile Memory Express (NVMe) Storage DevicesCurrent
April 2024
- RFC 9484Proxying IP in HTTPCurrent
October 2023
- RFC 9584RTP Payload Format for Essential Video Coding (EVC)Current
June 2024
- RFC 9595YANG Schema Item iDentifier (YANG SID)Current
July 2024
- RFC 9599Guidelines for Adding Congestion Notification to Protocols that Encapsulate IPCurrent
August 2024
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?