- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 4 May 2016 16:02:49 +1000
- To: RFC Errata System <rfc-editor@rfc-editor.org>
- Cc: Roy Fielding <fielding@gbiv.com>, "Julian F. Reschke" <julian.reschke@greenbytes.de>, Ben Campbell <ben@nostrum.com>, Alissa Cooper <alissa@cooperw.in>, aamelnikov@fastmail.fm, quae@daurnimator.com, ietf-http-wg@w3.org
Held for Document Update. Please make suggestions through the Working Group's issue tracker for HTTP/1.1 <https://github.com/httpwg/http11bis/issues>, not the errata system. > On 4 May 2016, at 3:54 PM, RFC Errata System <rfc-editor@rfc-editor.org> wrote: > > The following errata report has been submitted for RFC7230, > "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=7230&eid=4683 > > -------------------------------------- > Type: Technical > Reported by: Daurnimator <quae@daurnimator.com> > > Section: 4 > > Original Text > ------------- > > > Corrected Text > -------------- > The name part of a transfer-parameter is case insensitive and MUST not > be "q" (as this would be ambiguous when used as part of the TE header). > > Notes > ----- > Nothing is said about how to handle transfer-parameters. > Notably, nothing is said about the case sensitivity of the parameter key. > > This results in a conflict with the TE header: if you see a "q" token, > you cannot know if it is a transfer-parameter vs a t-ranking. > > It *is* noted that the "q" token is case insensitive in section 4.3. >> When multiple transfer codings are acceptable, the client MAY rank >> the codings by preference using a case-insensitive "q" parameter > > 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 (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC7230 (draft-ietf-httpbis-p1-messaging-26) > -------------------------------------- > Title : Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing > Publication Date : June 2014 > Author(s) : R. Fielding, Ed., J. Reschke, Ed. > Category : PROPOSED STANDARD > Source : Hypertext Transfer Protocol Bis APP > Area : Applications > Stream : IETF > Verifying Party : IESG > -- Mark Nottingham https://www.mnot.net/
Received on Wednesday, 4 May 2016 06:03:23 UTC