You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
I'm getting
Error: Error loading ICU asset.
while addingBlazorWasmAntivirusProtection
that runs under Azure WAF.This is how it looks like:
Another question is whether it's confirmed that
BlazorWasmAntivirusProtection
works successfully with Azure WAF?Steps to reproduce:
dotnet new blazorwasm -n test
dotnet add package BlazorWasmAntivirusProtection
Publish, upload to Azure AppService that secured with WAF.
Project
.csproj
looks like this:The text was updated successfully, but these errors were encountered: