- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Thu, 7 Jun 2018 06:03:07 -0700 (PDT)
- To: julian.reschke@greenbytes.de, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, mnot@mnot.net, pmcmanus@mozilla.com
- Cc: magnar@myrtveit.com, ietf-http-wg@w3.org, rfc-editor@rfc-editor.org
The following errata report has been submitted for RFC6266,
"Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)".
--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata/eid5383
--------------------------------------
Type: Technical
Reported by: Parameter names must not allow * <magnar@myrtveit.com>
Section: 4.1
Original Text
-------------
disp-ext-parm = token "=" value
| ext-token "=" ext-value
ext-token = <the characters in token, followed by "*">
Defined in [RFC2616]:
token = <token, defined in [RFC2616], Section 2.2>
quoted-string = <quoted-string, defined in [RFC2616], Section 2.2>
value = <value, defined in [RFC2616], Section 3.6>
; token | quoted-string
Defined in [RFC5987]:
ext-value = <ext-value, defined in [RFC5987], Section 3.2>
Corrected Text
--------------
disp-ext-parm = parmname "=" value
| ext-parmname "=" ext-value
ext-parmname = <the characters in parmname, followed by "*">
Defined in [RFC2616]:
quoted-string = <quoted-string, defined in [RFC2616], Section 2.2>
value = <value, defined in [RFC2616], Section 3.6>
; token | quoted-string
Defined in [RFC5987]:
parmname = <parmname, defined in [RFC5987], Section 3.2>
ext-value = <ext-value, defined in [RFC5987], Section 3.2>
Notes
-----
RFC5987 section 3.2.1 modifies the grammar from RFC2616. These modifications should be used in RFC6266. If not, it is impossible to determine whether a parameter should be a value or an ext-value based on the parameter name, since "*" is a valid character in token.
Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party
can log in to change the status and edit the report, if necessary.
--------------------------------------
RFC6266 (draft-ietf-httpbis-content-disp-09)
--------------------------------------
Title : Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)
Publication Date : June 2011
Author(s) : J. Reschke
Category : PROPOSED STANDARD
Source : Hypertext Transfer Protocol Bis APP
Area : Applications
Stream : IETF
Verifying Party : IESG
Received on Thursday, 7 June 2018 13:04:04 UTC