Blazor Wasm is not Caching DLL files when loaded from IFrame

[avichhetri8]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I loaded the blazor product using IFrame and the DLL files were not cached. All the Dll files were downloaded after refreshing the page.

Loaded using IFrame

Loaded directed using Url: It was able to cache the DLL files

Expected Behavior

DLL files must be cache when loaded using IFrame

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

6

Anything else?

No response

[javiercn]

@avichhetri8 thanks for contacting us.

It might be that your iframe is not considered a securecontext and the cache APIs are not available there. I would set a breakpoint in your iframe and check if the CacheStorage API is available there.

Blazor does not make any distinction on whether the app is running inside an iframe or not.

[avichhetri8]

hello @javiercn , i simple using example.html with code <iframe title='library-manager-iframe' src ='https://localtest.appservice.qc.com:5000/libmanager/index/10000001' /> to load a page. Blazor project was successfully loaded but, in cache storage nothing is cache

[javiercn]

@avichhetri8 I was suggesting that you open the developer tools and check if the actual API is available on the iframe. That's likely the reason blazor is not caching the dlls.

Hi @avichhetri8. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

See our Issue Management Policies for more information.