W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2022

Re: [Technical Errata Reported] RFC9110 (7138)

From: Julian Reschke <julian.reschke@gmx.de>
Date: Tue, 1 Nov 2022 16:50:55 +0100
Message-ID: <18a78dd0-fd42-bf94-c406-980e00bcdd34@gmx.de>
To: ietf-http-wg@w3.org
On 23.09.2022 15:17, RFC Errata System wrote:
> The following errata report has been submitted for RFC9110,
> "HTTP Semantics".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid7138
>
> --------------------------------------
> Type: Technical
> Reported by: Yousouf Taghzouti <yousouf.taghzouti@emse.fr>
>
> 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).
>
> 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.
>
> --------------------------------------
> 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

IMHO this erratum should be set to "verified".

Best regards, Julian
Received on Tuesday, 1 November 2022 15:51:10 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:44:08 UTC