RFC 9532 · PROPOSED STANDARD · 2024
SUN · 14 JUN 2026
HTTP Proxy-Status Parameter for Next-Hop Aliases
Overview
RFC 9532, “HTTP Proxy-Status Parameter for Next-Hop Aliases”, is a Proposed Standard document published in January 2024 by T. Pauly. The canonical text is published by the RFC Editor.
Abstract
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.
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
Read this RFC
The canonical text of RFC 9532 is hosted at rfc-editor.org. Available in HTML,TXT,PDF,XML.
Other RFCs from 2024
- RFC 9531 Path Steering in Content-Centric Networking and Named Data Networking
- RFC 9533 One-Way and Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group
- RFC 9530 Digest Fields
- RFC 9534 Simple Two-Way Active Measurement Protocol Extensions for Performance Measurement on a Link Aggregation Group
- RFC 9529 Traces of Ephemeral Diffie-Hellman Over COSE
- RFC 9535 JSONPath: Query Expressions for JSON
- RFC 9528 Ephemeral Diffie-Hellman Over COSE
- RFC 9536 Registration Data Access Protocol Reverse Search