RFC 8188 · PROPOSED STANDARD · 2017
TUE · 15 SEP 2026
Encrypted Content-Encoding for HTTP
Overview
RFC 8188, “Encrypted Content-Encoding for HTTP”, is a Proposed Standard document published in June 2017 by M. Thomson. The canonical text is published by the RFC Editor.
Abstract
This memo introduces a content coding for HTTP that allows message payloads to be encrypted.
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 8188 is hosted at rfc-editor.org. Available in TXT,HTML.
Other RFCs from 2017
- RFC 8187 Indicating Character Encoding and Language for HTTP Header Field Parameters
- RFC 8189 Multi-Cost Application-Layer Traffic Optimization
- RFC 8186 Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol
- RFC 8190 Updates to the Special-Purpose IP Address Registries
- RFC 8185 Dual-Homing Coordination for MPLS Transport Profile Pseudowires Protection
- RFC 8191 Home Network Prefix Renumbering in Proxy Mobile IPv6
- RFC 8192 Interface to Network Security Functions : Problem Statement and Use Cases
- RFC 8184 Dual-Homing Protection for MPLS and the MPLS Transport Profile Pseudowires