<p>I have an emberjs application which has been deployed and in google chrome browser im getting the following errors for 2 of the .js files.</p>
<blockquote>
<p>Failed to find a valid digest in the 'integrity' attribute for
resource
'http://staging.org.com/assets/vendor-0ada2c9fb4d3e07ad2f0c6a990945270.js'
with computed SHA-256 integrity
'Sb4Xc/Oub27QW0MKlqK0sbq0Mm476jU7MgJaCzd/gKk='. The resource has been
blocked</p>
</blockquote>
<p>When i inspect the file i can see script tags for the two .js files in question. I'm not 100% sure how this integrity check works. You can see the integrity attribute below with the sha's.</p>
<pre><code>&lt;script src=&quot;/assets/vendor-0ada2c9fb4d3e07ad2f0c6a990945270.js&quot; integrity=&quot;sha256-s3XY9h9v9IThygF6UkWRvWZsf7zeTqYJ1rLfDgg1bS0= sha512-k3lfqdeZw3OcsECfD3t99Hidh6IoRlFSoIu5nJk0FkLYHwx0q/rddirj4jh4J73dmLwKfG9mx0U5Zf6ZzRBsvA==&quot; &gt;&lt;/script&gt;
&lt;script src=&quot;/assets/g-web-56670cf0485cf52f54589091e2a25cc8.js&quot; integrity=&quot;sha256-jNmWqO61OPijscQ5cHVSbB1Ms5wKX78ZACYdhrUo3X4= sha512-oiksgRFsqgHaCvXPvd3SAsUuX4zPeVClQBIgrOgIKNBMa3hPqCHknoFqDGRtSyfN4EdIkfk/x1zSqBqRvONAGQ==&quot; &gt;&lt;/script&gt;
</code></pre>
<p>The emberjs application is built using a docker image, deployed to kubernetes and an aws elb running haproxy is handling the routing for this application such that when i navigate to <code>staging.x.com</code> it routes to the internal dns in kubernetes of this service (emberjs web app).</p>
<p>What's interesting to note;</p>
<ol>
<li>Running <code>ember serve</code> locally works and the applications loads fine.</li>
<li>Building and running the docker image locally works and the applications loads fine.</li>
</ol>
<p>The issue is only occurring on my deployed staging environment.</p>

<p>I got this error when deploying a Blazor WebAssembly app.</p>
<blockquote>
<p>Failed to find a valid digest in the 'integrity' attribute for
resource</p>
</blockquote>
<p>And then it showed several NuGets. Manually deleted all <code>bin</code> and <code>obj</code> folders in the solution and then redeployed. After this everything worked.</p>
<p><a href="https://github.com/dotnet/aspnetcore/issues/28692#issuecomment-783333400" rel="noreferrer">https://github.com/dotnet/aspnetcore/issues/28692#issuecomment-783333400</a></p>
