Re: [whatwg/fetch] CORB: nosniff handling (#686)

> This seems unfortunate, but may be still be the right way to proceed. WDYT?

If an implementation would not put it there, but have all CORB-related checks together, I'd be more inclined to match that, probably. Even if we create that algorithm incrementally. That'd also more directly tie it to "no-cors".

> I still think that the difference between net-error-VS-empty-body is not observable for images

Reading https://html.spec.whatwg.org/multipage/semantics.html#obtaining-a-resource-from-a-link-element which @domenic pointed out strongly suggests that it distinguishes between 200/network error for `<link rel=preload as=image>` and doesn't much care whether it got an actual image.

-- 
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/pull/686#issuecomment-378228038