Tests failures caused by wrong integrity hash for js file (SRI)

[pitgrap]

We started securing our websites with integrity="<hash>" entries for all JS and CSS files. Everything works fine, if you visit the pages with any browser.

But our cypress tests stopped working because the main JS file has been blocked with a different hash than in the HTML.

Example error:

Failed to find a valid digest in the 'integrity' attribute for resource 'https://mydomain/main.js' with computed SHA-512 integrity '/pV2IMn1pHSGTOsdjZDMp8pXeam93tFXyL0w/E+e1wUQ60iuIXvk+gWWzOVn84CsptqbK9zlL2gjzm2XRqCl/g=='. The resource has been blocked.

The hash of the file is sha512-6gIXUlsHN2MhnhvvaDN+5j4g3z33V4fPCahbrhzvCSDHVJ4tx2F0KK2bNJHa3yo6NNMjtkMYbcTK/nd+ki9qlA==. Why did it change?

I checked the documentation and all I found, are these two configs:

  chromeWebSecurity: false,
  experimentalModifyObstructiveThirdPartyCode: true,

But they didn't fix the problem. :(

How can I get my tests running back again?

[pitgrap]

Ok, probably found a solution.
the setting experimentalSourceRewriting: true fixed it.

The documentation https://docs.cypress.io/guides/references/experiments#Configuration is somehow misleading. experimentalModifyObstructiveThirdPartyCode is related to SRI, but didn't fix it.

[pitgrap]

See also #29111