RFC 7231, "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content", June 2014

Note: This RFC has been obsoleted by RFC 9110

Errata ID: 4689
Status: Held for Document Update
Type: Technical
Publication Format(s) : TEXT
Reported By: Daurnimator
Date Reported: 2016-05-10
Held for Document Update by: Alexey Melnikov
Date Held: 2017-02-23

Section 3.1.1.2 says:

3.1.1.2.  Charset

   HTTP uses charset names to indicate or negotiate the character
   encoding scheme of a textual representation [RFC6365].  A charset is
   identified by a case-insensitive token.

     charset = token

   Charset names ought to be registered in the IANA "Character Sets"
   registry (<http://www.iana.org/assignments/character-sets>) according
   to the procedures defined in [RFC2978].

It should say:

3.1.1.2.  Charset

   HTTP uses charset names to indicate or negotiate the character
   encoding scheme of a textual representation [RFC6365].


     charset       = <mime-charset, see [RFC5987], Section 3.2.1>


   Charset names ought to be registered in the IANA "Character Sets"
   registry (<http://www.iana.org/assignments/character-sets>) according
   to the procedures defined in [RFC2978].

Notes:

The definition of charset from RFC 5987 is more strict and more correct.

Mark Nottingham: This is not an errata; it is a suggestion for a technical change in the document, and needs to be discussed by the working group.

Report New Errata