The cache in the WebAssemblyResourceLoader and also the memory snapshot creates different cache for each app.
The current logic takes index.html?item=123 out of http://localhost:53504/index.html?item=123 as cache name.
Therefore the cache is not loaded when user arrived from external deep link item=123 or if the same app has multiple html pages.
If we fully migrate to assets hashes in the asset name, we could drop WebAssemblyResourceLoader.
But the problem would stay for memory snapshot.
@maraf suggested that we could generate Application GUID during build. I guess we would put it into the boot.config.json ?
The cache in the
WebAssemblyResourceLoaderand also the memory snapshot creates different cache for each app.The current logic takes
index.html?item=123out ofhttp://localhost:53504/index.html?item=123as cache name.Therefore the cache is not loaded when user arrived from external deep link
item=123or if the same app has multiple html pages.If we fully migrate to assets hashes in the asset name, we could drop
WebAssemblyResourceLoader.But the problem would stay for memory snapshot.@maraf suggested that we could generate Application GUID during build. I guess we would put it into the
boot.config.json?