Blazor wasm caching issue

[codemahek]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

So the whole issue started with this ticket
#64009
And in the latest version i.e. 10.0.2, it has been fixed and now its caching the wasm properly.
Now the issue is slightly different.
Once you open the Blazor wasm, it will get the wasm from cache and even the dotnet.js from the cache which is perfect.
Now keep the page open for sometime and refresh it, now for wasm it will still fetch it from cache but dotnet.js it gives 304.
So seems there is some timeout

Expected Behavior

if nothing is changed, instead of 304 it should get it from cache

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

10.0.2

Anything else?

No response

[javiercn]

@codemahek thanks for contacting us.

Is this wasm standalone or hosted? Are you using the ImportMap component? In the absence of ImportMap our Blazor script will import dotnet.js and that will contain headers to force the revalidation.

Otherwise, when you update to let's say 10.0.3, your users might get a stale dotnet.js which could potentially break their app. The logic is that fingerprinted assets gets cached forever and non-fingerprinted assets get revalidated. dotnet.js has always been imported directly from javascript by Blazor using a plain import, so this is existing behavior all the way up to the initial blazor version.

[codemahek]

@javiercn thanks that works.

[codemahek]

another thing which I have, if you have the wasm which is marked as lazy loaded.
And if for that wasm if there are any js and css file in the app.razor, than it will never be fingerprinted even after adding in the @assets