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

simoneonofri left a comment (whatwg/fetch#1854)

Hi all, thanks for your patience, [following up on the TAG discussion](https://github.com/w3ctag/design-reviews/issues/1203) and the discussion in SING.

After checking this PR, I think the issue's immediate concern is no longer present in that patch:
- no-cors -specific handling was removed
- no-cors requests fall back before dictionary negotiation;
- registration is limited to non-opaque responses in secure contexts
- an opaque dictionary-compressed response produces a network error

And this is in line with [RFC 9842 Section 9.3.2](https://www.rfc-editor.org/rfc/rfc9842.html#section-9.3.2) boundary.

If opaque-response support returns in a separate proposal, however, `CORP: cross-origin` would not be an equivalent signal, as it permits a no-cors response to pass CORP but does not make it CORS-readable.

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

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