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

@guohuideng2024 commented on this pull request.



> @@ -5004,6 +5041,15 @@ steps:
 
      <li><p>Let <var>type</var> be <var>blob</var>'s {{Blob/type}}.
 
+     <li><p>Let <var>coding</var> be the empty string.
+
+     <li><p>Let <var>accept-coding</var> be the result of <a for="header list">getting</a>
+        `<code>Accept-Encoding</code>` from <var>request</var>'s <a for=request>header list</a>.
+        If <var>accept-encoding</var> is not null and the server selects one of the encoding options,
+        set <var>coding</var> to the selected encoding option; otherwise, i.e., no encoding is used,
+        set <var>coding</var> to <a href=https://httpwg.org/specs/rfc9110.html#field.accept-encoding>
+        <code>"identity"</code></a>.

Thanks guys for pointing out this is on client side. I thought I was on server side. :( 
Also Noam and I had discussion offline. All the filtering happens after fetch. So we don't filter the values here.
I changed the text accordingly.


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

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