What is the 'SubResource Integrity (SRI)' hash format and what happens when the hash doesn't match?

• A.The SRI format is integrity='sha384-{hex-encoded-hash}'. If the browser downloads the resource and the computed hash doesn't match the declared value, the browser loads the resource anyway and logs a console warning (if devtools is open). The page continues loading with the modified resource
• B.SRI uses the format integrity='sha384-{base64-encoded-hash}'. If the browser downloads the resource and the computed hash doesn't match the declared value, the browser refuses to load or execute the resource and generates a CSP-style violation report (if report-uri is configured). The page continues loading without the failed resource
• C.SRI hashes are carried by crossorigin='sha384-{base64-encoded-hash}'. If the browser downloads the resource and the computed hash doesn't match the declared value, the browser retries from the origin server and falls back to the cached copy (if the retry fails). The page continues loading with the cached resource