Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error loading ICU asset #30

Open
sergeyzwezdin opened this issue Oct 25, 2022 · 2 comments
Open

Error loading ICU asset #30

sergeyzwezdin opened this issue Oct 25, 2022 · 2 comments

Comments

@sergeyzwezdin
Copy link

I'm getting Error: Error loading ICU asset. while adding BlazorWasmAntivirusProtection that runs under Azure WAF.

This is how it looks like:

2022-10-25 at 16 42 05

Another question is whether it's confirmed that BlazorWasmAntivirusProtection works successfully with Azure WAF?

Steps to reproduce:

  1. dotnet new blazorwasm -n test
  2. dotnet add package BlazorWasmAntivirusProtection

Publish, upload to Azure AppService that secured with WAF.

Project .csproj looks like this:

<Project Sdk="Microsoft.NET.Sdk.BlazorWebAssembly">

  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <Nullable>enable</Nullable>
    <ImplicitUsings>enable</ImplicitUsings>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="BlazorWasmAntivirusProtection" Version="1.8.5" />
    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly" Version="6.0.7" />
    <PackageReference Include="Microsoft.AspNetCore.Components.WebAssembly.DevServer" Version="6.0.7" PrivateAssets="all" />
  </ItemGroup>

</Project>
@FiberKaliber
Copy link

@sergeyzwezdin We are facing the exact same error with this package under Azure WAF, did you find any solution to this?

@FiberKaliber
Copy link

FiberKaliber commented Feb 13, 2023

@sergeyzwezdin Our devops team found out that Azure WAF where still blocking requests but this time for .dat and .blat files.
Easiest way to find these is to look at "runtime": { ... } in ".../publish/wwwroot/_framework/blazor.boot.json".

The only solution we found was to specify a custom network rule in Azure WAF for these specific files to be allowed for request for our host. This is not optimal but no available configuration on this package seemed to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants