Alright, apologies for the chatter here (but not really :)) as I mentioned this is about a week's worth of work sort of culminating in one day. The problem I am facing now is the Blazor-routed responses. I am seeing both 302s and 503s. Unfortunately, the FileLoadException is no longer occurring so that does not seem to be related here. I have been following the diagnostics prescribed here:
I have been able to get 503s from there, but nothing says exactly what is causing them. I am also seeing those 302s for
HostnameSyncPinger in HTTP logs. There is no location provided so not sure where they are redirecting. I will get those logs and attach them to your private message @Ryan Hill .
The good news is that I further explored the MVC routes and they are WICKED fast now and work exactly like I would expected a warmed-up request to behave. It was so fast I thought the swap didn't happen :D But the staging took 16 seconds (!) to load so things work there, but not in Blazor.
Finally, I got my SignalR warmed up as well. So, kicking some doors down, and the last one seems to be this Blazor routing issue.