Re: [whatwg/fetch] CORS readability for no-cors requests (Issue #1839)

pmeenan left a comment (whatwg/fetch#1839)

@noamr mentioned that it sounds a lot like [CORP](https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Cross-Origin_Resource_Policy) which is there to provide a way to block side-channel (Spectre) attacks for no-cors requests.

If it's not overloading the existing CORP (since it's protecting against the same thing), we could unlock dictionary support for no-cors requests in two ways:

1. Rely on opt-in for sidechannel protection with CORP and just allow dictionary compression for all no-cors requests with CORP blocking the requests that explicitly opt-in to sidechannel attack protection.
2. Default to safe for no-cors but allow an explicit opt-in with `Cross-Origin-Resource-Policy: cross-origin` on the response header as a signal that it's explicitly safe.

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

Message ID: <whatwg/fetch/issues/1839/3524571107@github.com>