Re: [whatwg/fetch] Integrity-metadata should not be a preload key (PR #1418)

> Same-origin script with non-matching digest

That test has a good digest for preload and a bad one for consume, and it shows that the preload is ignored.
"not CORS request, with correct hash" tests the main use-case here; that even when the consumer doesn't specify integrity metadata, the preload (which does have integrity metadata) can be used.

There is a test missing to show that if both preload and consumer have matching integrity but with a different SHA the preload should be consumed. It's an edge case that IIRC Chromium currently doesn't implement due to it being esoteric, I can add a test for it and open a bug.

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

Message ID: <whatwg/fetch/pull/1418/c1076323769@github.com>