RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

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

Note: This RFC has been obsoleted by RFC 9110

Source of RFC: httpbis (wit)

Errata ID: 6019
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT

Reported By: Michael Osipov
Date Reported: 2020-03-16
Rejected by: Barry Leiba
Date Rejected: 2020-07-10

Section 3.1.1.1 says:

 A parameter value that matches the token production can be
   transmitted either as a token or within a quoted-string.  The quoted
   and unquoted values are equivalent.  For example, the following
   examples are all equivalent, but the first is preferred for
   consistency:

     text/html;charset=utf-8
     text/html;charset=UTF-8
     Text/HTML;Charset="utf-8"
     text/html; charset="utf-8"

It should say:

 A parameter value that matches the token production can be
   transmitted either as a token or within a quoted-string.  The quoted
   and unquoted values are equivalent.  For example, the following
   examples are all equivalent, but the first is preferred for
   consistency:

     text/html;charset=utf-8
     text/html;charset=UTF-8

Notes:

Section 3.1.1.2 defines charset value to be a token. I consider this to be a bad example which might cause confusion. Why should I quote the value if it is defined as token?! You make want to use some other example.
--VERIFIER NOTES--
What's relevant is the ABNF for *parameter*, and that allows both token and quoted-string. So the example is correct.

Report New Errata



Advanced Search