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

@noamr commented on this pull request.



> @@ -5008,6 +5043,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-encoding</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>

In general this bit is conflating between request and response headers. It's not clear at which point "identity" is set exactly based on what the response headers are. This needs to work from the client-side perspective.

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

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