Re: [whatwg/fetch] Return a `content-encoding` header for resource timing and more (PR #1796)

@guohuideng2024 commented on this pull request.



> @@ -6319,6 +6321,20 @@ optional boolean <var>forceNewConnection</var> (default false), run these steps:
          <li><p>Let <var>codings</var> be the result of <a>extracting header list values</a> given
          `<code>Content-Encoding</code>` and <var>response</var>'s <a for=response>header list</a>.
 
+         <li><p>Let <var>filteredCoding</var> be "<code>unknown</code>".
+
+         <li><p>If <var>codings</var> is null, then set <var>filteredCoding</var> to the empty string.
+
+         <li><p>Otherwise, if <var>codings</var> contains two strings or more, then set <var>filteredCoding</var> to
+         "<code>multiple</code>".
+
+         <li><p>Otherwise, if <var>codings</var>[0] is the empty string, or it is supported by the user agent,
+         and is listed in the <a href="https://www.iana.org/assignments/http-parameters/http-parameters.xhtml#content-coding">
+         <cite>content encoding registry on IANA</cite></a>, then set <var>filteredCoding</var> to <var>codings</var>[0].

1. Yes all output should be lowercased and I made changes in text accordingly. Thanks for pointing out.
2. In the current text, a value is "allowed" as long as it "case insensitive matches" a registered value. And it will be lowercased before exposed.  Is it O.K.?

Thanks.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/pull/1796#discussion_r2043081589
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/pull/1796/review/2765915328@github.com>