Thank you all for your responses. The machine seems to have no bearing on the issue since this was an external network that reported and I was able to recreate locally. I know chrome is the latest version (80.0.3987.132) on my machine but unknown on client.
More information here is that when the session value timeout is low, then all is fine. As I increased the number, then the time to establish starts to increase. The local disk seems to just go wild and then there is a flash of a red and then the login appeared. I happened to go to a machine that was sitting since yesterday and it took minutes to get things going. So for the first phase nothing is occurring at all and the browser is just spinning. Then it finally figures out that the session is gone and then the server tries to issue a new session. This was that flash of red that I saw before but on this machine I was able to go deeper since the red was on the network monitor window for a long time. When I zoom in on it, it says that the connect is stalled.
The status is 500 and the document is $/js/IWBase__376527852.js. I have attached the js here so you can have a look at it. The IW log on the server just says Session ID is invalid which makes sense.
Looks like the attachment never uploaded so I edited this to just add with an image screen shot as of this morning. So the issue seems to really rear its head when I leave things overnight. The browser said this morning that it was waiting on the web site instead of just spinning. Is there something overnight that goes to sleep and takes a while to respond for an old session? Seems to be nothing to do with my code. No matter the server operation or page, the stall can occur. All works fine in Firefox overnight though which is the perplexing thing.
Cheers.
More information here is that when the session value timeout is low, then all is fine. As I increased the number, then the time to establish starts to increase. The local disk seems to just go wild and then there is a flash of a red and then the login appeared. I happened to go to a machine that was sitting since yesterday and it took minutes to get things going. So for the first phase nothing is occurring at all and the browser is just spinning. Then it finally figures out that the session is gone and then the server tries to issue a new session. This was that flash of red that I saw before but on this machine I was able to go deeper since the red was on the network monitor window for a long time. When I zoom in on it, it says that the connect is stalled.
The status is 500 and the document is $/js/IWBase__376527852.js. I have attached the js here so you can have a look at it. The IW log on the server just says Session ID is invalid which makes sense.
Looks like the attachment never uploaded so I edited this to just add with an image screen shot as of this morning. So the issue seems to really rear its head when I leave things overnight. The browser said this morning that it was waiting on the web site instead of just spinning. Is there something overnight that goes to sleep and takes a while to respond for an old session? Seems to be nothing to do with my code. No matter the server operation or page, the stall can occur. All works fine in Firefox overnight though which is the perplexing thing.
Cheers.