Re: [whatwg/fetch] Add support for compression dictionary transport (PR #1854)

@pmeenan commented on this pull request.



> +   <li><p>Let <var>corpPolicy</var> be the result of <a for="header list">getting</a>
+   `<a http-header><code>Cross-Origin-Resource-Policy</code></a>` from <var>response</var>'s
+   <a for=response>header list</a>.
+
+   <li><p>If <var>request</var>'s <a for=request>response tainting</a> is "<code>opaque</code>" and
+   <var>corpPolicy</var> is not `<code>cross-origin</code>`, then return <var>response</var>.

I went ahead and added a `compression dictionary disallowed` flag to `request` which is updated in `Main fetch` just after the `response tainting` is evaluated for each step and then the flag is just checked when doing dictionary-specific work (ignoring the `Use-As-Dictionary` header and erroring dictionary-compressed opaque responses.

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

Message ID: <whatwg/fetch/pull/1854/review/3792315658@github.com>