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

noamr left a comment (whatwg/fetch#1839)

> Even for responses that are CORS-readable today we try to limit the amount of information that is exposed (see https://github.com/w3c/resource-timing/issues/381 for instance) to avoid exposing more information to cross-origin scripts.
> 
> So making more responses CORS-readable without even opt-in from the website would go counter towards that goal. Perhaps if the scope of the readability is limited it could be reasonable.

Perhaps Content-Readability can be an explicit enum of how it can be used 

’Content-Readability: dictionary’ or some such where other values can be added if we deem them safe to expose to unaware websites 

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

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