New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrity check error with webpack runtime file #101
Labels
Comments
Hi, thanks for your detailed bug report. I can reproduce this and will see that I can fix it soon. |
jscheid
added a commit
that referenced
this issue
Jan 29, 2019
jscheid
added a commit
that referenced
this issue
Jan 30, 2019
jscheid
added a commit
that referenced
this issue
Jan 30, 2019
jscheid
added a commit
that referenced
this issue
Jan 30, 2019
@jscheid I tried your fix: including only lazy loaded chunks in the runtime file seems to fix this issue 👍 |
No problem. Released in version 1.3.2. |
This was referenced Mar 9, 2021
This was referenced Mar 16, 2021
Bump webpack-subresource-integrity from 1.0.4 to 1.5.2 in /ClientApp
paulostradioti/airplanesystem#3
Open
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
We started to use
webpack-subresource-integrity
plugin in my company, and I noticed some integrity errors because of our webpack runtime file and the browser cache. In some cases, it is possible to generate a runtime file with a name which does not change but where the content changed ([name].[contenthash].js
). So if the runtime file (with this same name) is in the user browser cache (because long term caching) and theindex.html
file is loaded with the new integritry hash (because no long term caching for index.html): an integrity error occurs.I created a repository in which you can reproduce this issue: https://github.com/sebastiendavid/webpack-sri-runtime-hash-issue
Steps to reproduce issue
runtime
file:src/modules/moduleA
content, for example:Before:
After:
runtime
file:build/runtime.94ebc40d8dbd2fa73811.js
.Notice that the hash in the filename did not change.
runtime
filesSubresource integrity hash from
app
chunk changed.runtime
filename did not change, but the content did. So if this file is cached by the browser and loaded from this cache: an integrity error occurs.The text was updated successfully, but these errors were encountered: