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

@noamr commented on this pull request.



> @@ -3945,7 +3948,6 @@ Content-Type:
 </div>
 </div>
 
-

Keep the new line

> @@ -1176,6 +1178,7 @@ is a <a>byte-case-insensitive</a> match for one of
    <li>`<a http-header><code>Access-Control-Request-Headers</code></a>`
    <li>`<a http-header><code>Access-Control-Request-Method</code></a>`
    <li>`<code>Connection</code>`
+   <li>`<code>Content-Encoding</code>`

Is this needed?

> @@ -6319,6 +6321,9 @@ 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>Set <var>response</var>'s <a for=response>body info</a>'s
+         <a for="response body info">content encoding</a> to <var>codings</var>.

Do UAs today do any observable processing to this "codings" value? What happens when there are multiple values? Resource timing would make this more observable so it needs to be specified

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

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