Hello,
Our team is currently developing web applications using Blazor WASM and has been struggling with the performance of their initial loading, especially on mobiles (time to interactive above fifty seconds), which our applications will mostly be used on.
We have tried compression using gzip and caching of some API calls with limited success.
Would you have other solutions to recommend for initial loading performance improvements, particularly on mobiles?
Otherwise, do you have a roadmap for performance improvements on your side? If so, what does it look like in terms of schedule and scope?
Finally, please do let us know if Blazor WASM is not the right choice for us and another framework would be better suited.
Thank you.
I was able to fix the issue by specifying the URL directly to the Identity Server in the OnApplicationInitialization
This seems a little like it's a hack but it worked for me.
Thanks for the help!
The app registration only has 2 redirects and doesn't let me configure anything else than an HTTPS URL. It's configured to use ID Tokens and is Multitenant enabled.
Let me know if you need anything more specific.
I also have these console issues that come up when accessing my dev environment! They seem to be related!
Thanks
If you're creating a bug/problem report, please include followings:
Hi,
I'm currently trying to use Azure AD authentication using the Option 2 (AddMicrosoftIdentityWebApp) provided in the Community post. https://community.abp.io/posts/how-to-use-the-azure-active-directory-authentication-for-mvc-razor-page-applications-4603b9cf?_ga=2.233242457.671860167.1658432542-369280404.1658432542
It worked perfectly on my local machine until I had to deploy the app in the Azure environment.
I'm getting the AADSTS50011 authentication error specifying the my redirect URIs are not matching between what's configured in the App Registration and what's provided from the app.
From the message received, I can see that Azure is trying to call my backend over HTTP instead of HTTPS. When I'm looking at my network traffic, I do see that the redirect_uri parameter from the URL is encoded over HTTP!
Tried solving this issue from the FAQs in the previous link and started having issues with the AzureAd:CallbackPath setting. It doesn't allow to put anything that isn't starting with a "/", so the proposed solution to specify an HTTPS return URL isn't going to work.
I'm running the code in an docker container within a Azure App Service running linux.
Any guidance will be greatly appreciated. Thanks
