runtime: icudt_EFIGS.dat blocked by firewall
We have integrated the dotnet.js Wasm runtime (.NET 8) into our existing Angular front-end app but we’re having issue with the icudt_EFIGS.dat file being blocked by the firewall.
Failed to load resource: the server responded with a status of 403 (forbidden)
Is there a workaround for this? A way to use another extension for that file maybe?
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 52 (30 by maintainers)
@ts-indikaf I have created a sample that uses custom extension for ICU using some of the new APIs added in .NET 8 https://github.com/maraf/dotnet-wasm-rename-icu
It doesn’t change the content/structure of ICU files like webcil does for assemblies, it only changes the extenion
@maraf that’s great. Thanks again.
Maybe you want to update the ReadMe file per project configs, for future reference? Just a suggestion. Unfortunately, I cannot update and push it into your repo due to access restrictions.
@ilonatommy @maraf yes, that was the issue. Thanks!
Confirmed on windows
This might be connected with https://github.com/dotnet/runtime/issues/92335. Could you place your project in a path with no spaces? I mean
C:\WORKING\Repo\Web Assembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csproj->C:\WORKING\Repo\WebAssembly\DotNet8rc1PublishTest\DotNet8rc1PublishTest.csprojYou should omit dotnet files from bundling with webpack. I was investigating integration with react/webpack last year https://github.com/maraf/dotnet-wasm-react and the rest was that until we have a single file solution https://github.com/dotnet/runtime/issues/86162, there isn’t a good way to integrate with it, as it rewrites all imports and URLs in sources. We have this sample that bundles dotnet files with webpack, but it requires extra configuration https://github.com/dotnet/runtime/tree/d67314ee8018b27748a8d0a1f4e38172ff680599/src/mono/sample/wasm/browser-webpack
We have all imports annotated in sources to be ignored by webpack, but they might get dropped when the runtime is built in release configuration. I’ll investigate it
https://github.com/dotnet/runtime/blob/d67314ee8018b27748a8d0a1f4e38172ff680599/src/mono/wasm/runtime/loader/run.ts#L389
@maraf thanks for your reply. We’re using pure WebAssembly, not Blazor though