Indicating Character Encoding and Language for HTTP Header Field Parameters
RFC 8187, “Indicating Character Encoding and Language for HTTP Header Field Parameters”, is a Proposed Standard document published in September 2017 by J. Reschke. It obsoletes RFC 5987. The canonical text is published by the RFC Editor.
Abstract
By default, header field values in Hypertext Transfer Protocol (HTTP) messages cannot easily carry characters outside the US-ASCII coded character set. RFC 2231 defines an encoding mechanism for use in parameters inside Multipurpose Internet Mail Extensions (MIME) header field values. This document specifies an encoding suitable for use in HTTP header fields that is compatible with a simplified profile of the encoding defined in RFC 2231.
This document obsoletes RFC 5987.
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.
The canonical text of RFC 8187 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8186 Support of the IEEE 1588 Timestamp Format in a Two-Way Active Measurement Protocol
- RFC 8188 Encrypted Content-Encoding for HTTP
- RFC 8185 Dual-Homing Coordination for MPLS Transport Profile Pseudowires Protection
- RFC 8189 Multi-Cost Application-Layer Traffic Optimization
- RFC 8184 Dual-Homing Protection for MPLS and the MPLS Transport Profile Pseudowires
- RFC 8190 Updates to the Special-Purpose IP Address Registries
- RFC 8183 An Out-of-Band Setup Protocol for Resource Public Key Infrastructure Production Services
- RFC 8191 Home Network Prefix Renumbering in Proxy Mobile IPv6