Describe the bug
Blazor WebAssembly 3.2.0 breaks the integrity of published modules.
To Reproduce
Upgraded a project to the Blazor RC and published it to Azure. No code was changed. The project runs fine locally but does not load from Azure.
Browser shows the following error messages. Seems that the integrity of some dlls cannot be verified. I rebuild multiple times, always with the same effect.
Failed to find a valid digest in the 'integrity' attribute for resource 'https://penet.azureedge.net/_framework/_bin/Microsoft.JSInterop.WebAssembly.dll' with computed SHA-256 integrity 'ly0M2c3xTIQTThpFK82FfNKJVWZ/mdm+FkwD54DHwSQ='. The resource has been blocked.
penet.azureedge.net/:1 Unknown error occurred while trying to verify integrity.
blazor.webassembly.js:1 Uncaught (in promise) TypeError: Failed to fetch
penet.azureedge.net/:1 Failed to find a valid digest in the 'integrity' attribute for resource 'https://penet.azureedge.net/_framework/wasm/dotnet.wasm' with computed SHA-256 integrity 'OSdheaBxNsYucYoLcmeBrZy9KLhKDvhCPNyd7ZvEIUc='. The resource has been blocked.
penet.azureedge.net/:1 Unknown error occurred while trying to verify integrity.
blazor.webassembly.js:1 Streaming compilation failed. Falling back to ArrayBuffer instantiation.
blazor.webassembly.js:1 Uncaught (in promise) TypeError: Failed to fetch
I'm not sure if this is an Blazor RC problem or an Azure hosting problem, but as the only thing I changed is the Blazor version and everything else is the same, I assume something went from with the RC.
Describe the bug
Blazor WebAssembly 3.2.0 breaks the integrity of published modules.
To Reproduce
Upgraded a project to the Blazor RC and published it to Azure. No code was changed. The project runs fine locally but does not load from Azure.
Browser shows the following error messages. Seems that the integrity of some dlls cannot be verified. I rebuild multiple times, always with the same effect.
I'm not sure if this is an Blazor RC problem or an Azure hosting problem, but as the only thing I changed is the Blazor version and everything else is the same, I assume something went from with the RC.