- From: Mark Nottingham <mnot@mnot.net>
- Date: Sat, 18 Aug 2012 19:23:15 +1000
- To: RFC Errata System <rfc-editor@rfc-editor.org>
- Cc: julian.reschke@greenbytes.de, barryleiba@computer.org, presnick@qualcomm.com, mnot@pobox.com, jack@nottheoilrig.com, ietf-http-wg@w3.org
6266 doesn't refer to 5234; > This specification uses the augmented BNF (ABNF) notation defined in Section 2.1 of [RFC2616], including its rules for implied linear > whitespace (LWS). Therefore, invalid. Cheers, On 18/08/2012, at 6:34 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote: > > 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_search.php?rfc=6266&eid=3325 > > -------------------------------------- > Type: Editorial > Reported by: Jack Bates <jack@nottheoilrig.com> > > Section: 4.1 > > Original Text > ------------- > 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 > > Corrected Text > -------------- > 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 > > Instructions: > ------------- > This errata 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 (IESG) > 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 > Area : Applications > Stream : IETF > Verifying Party : IESG -- Mark Nottingham http://www.mnot.net/
Received on Saturday, 18 August 2012 09:23:41 UTC