Why can't dotnet.native.wasm be cached?

[yll690]

Hi, i'm using IIS as a static file server to host a avalonia web application. I found that all other WASMs can be cached, except for dotnet.native.u62l2yggd7.wasm, which is downloaded every time, taking 60MB data and dozens of seconds in poor network. I have checked the dotnet.js, all WASMs are obtained through globalThis.fetch function, and the parameters are same except for the URL.

The TargetFramework is net10.0-browser. AOT is enabled. The browser is Edge 143.

Is this behavior designed? Is there any way to change this behavior? The dotnet.native is so big even use compression.

This is the headers of first refresh:

This is the headers of second refresh:

[yll690]

In this case, the dotnet.native.wasm is about 18MB after compressed. If I enable the compression, It can be cached. Someone remind me that the file of 60MB is too large to be cached. I tested some files and found it make sense. The threadhold is about 25MB.

So is it the real reason? If the dotnet.native.wasm exceeds the threadhold after compressed, is there any way to cache it?

[yll690]

I found using ServiceWorker can cache large files manually. But I'm not sure if it is the best way.

[yll690]

If I use https instead of http (self-signed), small files also can not be cached. This may be caused by that in dotnet.js the fetch is called with "no-cache" parameter. However changing it to force-cache or using workaround like this does not help. It seems I have to wait this fix to release.

[yll690]

Small files can now be cached in 10.0.2.