- From: RFC Errata System <rfc-editor@rfc-editor.org>
- Date: Wed, 9 Nov 2022 00:34:16 -0800 (PST)
- To: yousouf.taghzouti@emse.fr, fielding@gbiv.com, mnot@mnot.net, julian.reschke@greenbytes.de
- Cc: francesca.palombini@ericsson.com, iesg@ietf.org, ietf-http-wg@w3.org, iana@iana.org, rfc-editor@rfc-editor.org
The following errata report has been verified for RFC9110,
"HTTP Semantics".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid7138
--------------------------------------
Status: Verified
Type: Technical
Reported by: Yousouf Taghzouti <yousouf.taghzouti@emse.fr>
Date Reported: 2022-09-23
Verified by: Francesca Palombini (IESG)
Section: 12.5.1
Original Text
-------------
The media type quality factor associated with a given type is
determined by finding the media range with the highest precedence
that matches the type. For example,
Accept: text/*;q=0.3, text/plain;q=0.7, text/plain;format=flowed,
text/plain;format=fixed;q=0.4, */*;q=0.5
would cause the following values to be associated:
Table 5:
Media Type Quality Value
text/plain;format=flowed 1
text/plain 0.7
text/html 0.3
image/jpeg 0.5
text/plain;format=fixed 0.4
text/html;level=3 0.7
Corrected Text
--------------
The media type quality factor associated with a given type is
determined by finding the media range with the highest precedence
that matches the type. For example,
Accept: text/*;q=0.3, text/plain;q=0.7, text/plain;format=flowed,
text/plain;format=fixed;q=0.4, */*;q=0.5
would cause the following values to be associated:
Table 5:
Media Type Quality Value
text/plain;format=flowed 1
text/plain 0.7
text/html 0.3
image/jpeg 0.5
text/plain;format=fixed 0.4
text/html;level=3 0.3
Notes
-----
To illustrate how the media type quality factor associated with a given type is determined, the following example is given:
Accept: text/*;q=0.3, text/plain;q=0.7, text/plain;format=flowed, text/plain;format=fixed;q=0.4, */*;q=0.5
The last row of the result table (table 5) presenting the values to be associated cannot be deduced (MediaType: text/html;level=3, Quality Value: 0.7), since only "text/*;q=0.3" and "*/*;q=0.5" are possible values and as explained in the RFC "text/*;q=0.3" should take precedence.
In section 5.3.2 of RFC7231, a similar example is given, where the last row of the table is correct (text/html;level=3 | 0.7) since in that example the accept header contains (text/html;q=0.7).
--------------------------------------
RFC9110 (draft-ietf-httpbis-semantics-19)
--------------------------------------
Title : HTTP Semantics
Publication Date : June 2022
Author(s) : R. Fielding, Ed., M. Nottingham, Ed., J. Reschke, Ed.
Category : INTERNET STANDARD
Source : HTTP
Area : Applications and Real-Time
Stream : IETF
Verifying Party : IESG
Received on Wednesday, 9 November 2022 08:34:30 UTC