RFC 7639: The ALPN HTTP Header Field
In plain English — editorial summary, not part of the RFC
This specification allows HTTP CONNECT requests to indicate what protocol is intended to be used within the tunnel once established, using the ALPN header field.
Document record
- Document ID
- RFC7639
- Published
- August 2015
- Authors
- A. Hutton; J. Uberti; M. Thomson
- 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 9931Security Considerations for Optimistic Protocol Transitions in HTTP/1.1Current
March 2026
- RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent
September 2015
- RFC 7604Comparison of Different NAT Traversal Techniques for Media Controlled by the Real-Time Streaming Protocol (RTSP)Current
September 2015
- RFC 7383Internet Key Exchange Protocol Version 2 (IKEv2) Message FragmentationCurrent
November 2014
- RFC 6887Port Control Protocol (PCP)Updated
April 2013
- RFC 8519YANG Data Model for Network Access Control Lists (ACLs)Current
March 2019
- RFC 6092Recommended Simple Security Capabilities in Customer Premises Equipment (CPE) for Providing Residential IPv6 Internet ServiceCurrent
January 2011
- RFC 5575Dissemination of Flow Specification RulesObsoleted
August 2009
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?