metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 8187: Indicating Character Encoding and Language for HTTP Header Field Parameters

In plain English — editorial summary, not part of the RFC

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.

Document record

Document ID
RFC8187
Published
September 2017
Authors
J. Reschke
Status
PROPOSED STANDARD
Stream
IETF
Area
wit
Pages
13
Also known as
—
Obsoletes:
RFC 5987

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/8187-indicating-character-encoding-and-language-for-http-header-field-parameters