metasystema.org
ObsoletedHISTORICIETF stream

RFC 5987: Character Set and Language Encoding for Hypertext Transfer Protocol (HTTP) Header Field Parameters

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8187.

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

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

By default, message header field parameters in Hypertext Transfer Protocol (HTTP) messages cannot carry characters outside the ISO- 8859-1 character set. RFC 2231 defines an encoding mechanism for use in Multipurpose Internet Mail Extensions (MIME) headers. This document specifies an encoding suitable for use in HTTP header fields that is compatible with a profile of the encoding defined in RFC 2231. [STANDARDS-TRACK]

Document record

Document ID
RFC5987
Published
August 2010
Authors
J. Reschke
Status
HISTORIC
Stream
IETF
Area
—
Pages
10
Also known as
—
Obsoleted by:
RFC 8187

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

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/5987-character-set-and-language-encoding-for-hypertext-transfer-protocol-http-header