tailblazor.dev is not loading

[umanivannan-conga]

I'm not sure whether this is the right place to create this, but creating this anyway.

[McNerdius]

Hmm strange... "works on my machine(s)". I wonder if it's an azure static web apps issue...

Thanks for letting me know, i'll look into it !

[McNerdius]

Not seeing any issues on azure portal, but this could be the issue:

https://stackoverflow.com/questions/66221439/blazor-webassembly-application-fails-to-load-due-to-integrity-errors

(Anonymous Browsing/Antivirus/Firewall blocking dll files)

The documented workaround is a bit hacky, though. Do any of the above scenarios apply ?

[umanivannan-conga]

Yeah i think its probably some security settings in my company provided laptop, I'm able to access the site from my mobile without issues.

[McNerdius]

OK thanks for the info. I'll be looking around for a more elegant solution than the published workaround this week, hopefully update tailblazor.dev & tailblazor.net repos this weekend, and mention it somewhere on tailblazor.dev.

[McNerdius]

So, i've applied the MS suggested workaround to the tailblazor.dev repo (issue / PR). The (hopeful) fix is hosted here, pending confirmation that the fix is a real, actual fix & PR merge. Then the fix gets applied to this repo, and so on.

[umanivannan-conga]

hI @McNerdius, Checked the fix, It looks like .bin extensions also seems to be blocked by our security vendor

[McNerdius]

Bummer :(

I have merged the "rename dll to bin" non-fix into tailblazor.dev - hopefully it will be the basis for a real fix, which will make its way here, into the tailblazor-templates. The hard part here is not knowing how to reproduce this security behavior on my end.

I'm working on a time-constrained commissioned project at the moment so i can't give this my full attention. I may be busy with that project as far out as mid-July(!), but i will be googling/stack-overflowing/discord-inquiring about it when i can.

In the meantime, i'm pinning this and #129 on the other repo. Hopefully there is a more robust yet still simple solution to be found. I wouldn't want to add a bunch of code to tailblazor-templates that only applies to one particular scenario, but it's certainly something i'd include in tailblazor.dev and its notes.