RFC 8188: Encrypted Content-Encoding for HTTP
In plain English — editorial summary, not part of the RFC
This memo introduces a content coding for HTTP that allows message payloads to be encrypted.
Document record
- Document ID
- RFC8188
- Published
- June 2017
- Authors
- M. Thomson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- wit
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9659Window Sizing for Zstandard Content EncodingCurrent
September 2024
- RFC 8164Opportunistic Security for HTTP/2Current
May 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 8673HTTP Random Access and Live ContentCurrent
November 2019
- RFC 7694Hypertext Transfer Protocol (HTTP) Client-Initiated Content-EncodingObsoleted
November 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?