You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I understand this new feature correctly, it will add a fingerprint to the name of static assets like CSS files or Javascript files. This means that whenever the file content changes, the fingerprint will change too. And this means that the browser will not load an old version of the file from cache but load the up-to-date version from the web server (because the name has changed). At the same time, when the file content does not change, the name will not change and so the browser can cache the static assets for a very long time (forever in theory).
I think we don't need the WithStaticAssets line because we are using Blazor and there it should be enabled automatically accordings to the link below.
Apollo3zehn
changed the title
Reduce issues with cached assets: Use Fingerprinted static web assets
Reduce issues with cached assets: Use fingerprinted static web assets
Aug 7, 2024
If I understand this new feature correctly, it will add a fingerprint to the name of static assets like CSS files or Javascript files. This means that whenever the file content changes, the fingerprint will change too. And this means that the browser will not load an old version of the file from cache but load the up-to-date version from the web server (because the name has changed). At the same time, when the file content does not change, the name will not change and so the browser can cache the static assets for a very long time (forever in theory).
I think we don't need the
WithStaticAssets
line because we are using Blazor and there it should be enabled automatically accordings to the link below.https://github.com/dotnet/core/blob/main/release-notes/9.0/preview/preview6/aspnetcore.md#fingerprinting-of-static-web-assets
The text was updated successfully, but these errors were encountered: