RFC 8164: Opportunistic Security for HTTP/2
In plain English — editorial summary, not part of the RFC
This document describes how "http" URIs can be accessed using Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive monitoring attacks. This mechanism not a replacement for "https" URIs; it is vulnerable to active attacks.
Document record
- Document ID
- RFC8164
- Published
- May 2017
- Authors
- M. Nottingham; M. Thomson
- Status
- HISTORIC
- Stream
- IETF
- Area
- wit
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8188Encrypted Content-Encoding for HTTPCurrent
June 2017
- RFC 8336The ORIGIN HTTP/2 FrameCurrent
March 2018
- RFC 7975Request Routing Redirection Interface for Content Delivery Network (CDN) InterconnectionCurrent
October 2016
- RFC 8470Using Early Data in HTTPCurrent
September 2018
- RFC 7838HTTP Alternative ServicesCurrent
April 2016
- RFC 7694Hypertext Transfer Protocol (HTTP) Client-Initiated Content-EncodingObsoleted
November 2015
- RFC 8673HTTP Random Access and Live ContentCurrent
November 2019
- RFC 7615HTTP Authentication-Info and Proxy-Authentication-Info Response Header FieldsObsoleted
September 2015
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?