RFC 7838: HTTP Alternative Services
In plain English — editorial summary, not part of the RFC
This document specifies "Alternative Services" for HTTP, which allow an origin's resources to be authoritatively available at a separate network location, possibly accessed with a different protocol configuration.
Document record
- Document ID
- RFC7838
- Published
- April 2016
- Authors
- M. Nottingham; P. McManus; J. Reschke
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 20
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7975Request Routing Redirection Interface for Content Delivery Network (CDN) InterconnectionCurrent
October 2016
- RFC 7694Hypertext Transfer Protocol (HTTP) Client-Initiated Content-EncodingObsoleted
November 2015
- RFC 7615HTTP Authentication-Info and Proxy-Authentication-Info Response Header FieldsObsoleted
September 2015
- RFC 7541HPACK: Header Compression for HTTP/2Current
May 2015
- RFC 7540Hypertext Transfer Protocol Version 2 (HTTP/2)Obsoleted
May 2015
- RFC 7538The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)Obsoleted
April 2015
- RFC 8164Opportunistic Security for HTTP/2Current
May 2017
- RFC 8188Encrypted Content-Encoding for HTTPCurrent
June 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?