RFC Errata
RFC 6266, "Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)", June 2011
Source of RFC: httpbis (wit)
Errata ID: 3325
Status: Rejected
Type: Editorial
Publication Format(s) : TEXT
Reported By: Jack Bates
Date Reported: 2012-08-18
Rejected by: Barry Leiba
Date Rejected: 2012-08-18
Section 4.1 says:
content-disposition = "Content-Disposition" ":" disposition-type *( ";" disposition-parm ) disposition-type = "inline" | "attachment" | disp-ext-type ; case-insensitive disp-ext-type = token disposition-parm = filename-parm | disp-ext-parm filename-parm = "filename" "=" value | "filename*" "=" ext-value 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
It should say:
content-disposition = "Content-Disposition" ":" disposition-type *( ";" disposition-parm ) disposition-type = "inline" / "attachment" / disp-ext-type ; case-insensitive disp-ext-type = token disposition-parm = filename-parm / disp-ext-parm filename-parm = "filename" "=" value / "filename*" "=" ext-value 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
Notes:
The grammar in the original text uses "|" to express alternation, but I think that only "/" is valid according to RFC 5234
Verifier notes: The grammar in 6266 is from RFC 2616, not from 5234. 6266 is correct as it stands.
--VERIFIER NOTES--
The grammar in 6266 is from RFC 2616, not from 5234. This text is correct as it stands.