Skip to main content

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

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'By default, header field values in Hypertext Transfer Protocol (HTTP) messages cannot easily carry characters outside …
Received changes through RFC Editor sync (changed abstract to '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.')
2017-09-14
(System)
Received changes through RFC Editor sync (created alias RFC 8187, changed abstract to 'By default, header field values in Hypertext Transfer Protocol (HTTP) messages …
Received changes through RFC Editor sync (created alias RFC 8187, changed abstract to '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.', changed pages to 13, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2017-09-14, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-httpbis-rfc5987bis and RFC 5987)
2017-09-14
(System) RFC published