This is starting to look like this issue, which also randomly started happening: https://support.aspnetzero.com/QA/Questions/8783/Login-Loop---Chrome-Fails---IE-Working---Hosted-In-IIS
I was not able to figure it out. What's most confusing is that it works fine for the my Production website in the same version of Chrome. Smells like some weird Chrome bug.
No, this is the only ABP project I am working on. Good to know about Chrome. It's not the first time I have seen something weird like this with Chrome.
Never mind, I think the problem is with Chrome caching. I have no idea what it's going, but it's using some aggressive caching techniques. I tried Private Mode and the issue persists. Then I tried IE and it works completely fine. Anyone else seen this issue?
Just chiming in here. I purchased AspNetZero for a smaller project and it's working great, but right now I am starting another project which is much more complicated. Javascript is my least favorite thing in the world and I shudder at the thought of having to debug another line of JS. Blazor is the only thing out there that really solves this problem. I am looking forward to news on this topic.
I will try that. Thank you!
No, I am not sure why this may be happening. It is very sporadic and is happening only a handful of times per day. I have a lot of users.
No, it is an issue with Flurl specifically not supporting Http 2.0. Once I change the Azure website back to Http 1.1, everything works fine. So I will just use 1.1 for now.
Changing the Azure http version for my website from 2 to 1.1 fixed the problem. It seems the latest version of Flurl does not support http2, which is very odd. Do you guys have a different version of AbpApiClient.cs that does not use Flurl? Maybe HttpClient?
I didn't know about that, thanks! Closing again.