Re: [whatwg/fetch] More CORB-protected MIME types - adding protected types one-by-one. (#860)

> I do think it would be nice if we could switch the error handling as per #727. Currently CORB sticks out a bit and I don't think it's needed, even though the change would be somewhat observable.

Hmmm... maybe this could be approach by changing how Fetch spec describes handling of "Cross-Origin-Resource-Policy" header (i.e. CORP not CORB).  CORP already results in errors.  And we could add new steps between steps 2 and 3 (after checking that this is a cross-origin, no-cors request) saying:
- Extract "Content-Type"
- If "Content-Type" is "PDF" (or X, Y, Z), then return "blocked".

WDYT?

cc @johnwilander @youennf 

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