We didn't have this problems when we used Classic, so I was hoping I could get some help with understanding the nechanism so we can fix it.
On the new app (.threads) we're having problems with the site freezing when used on the company network after the user logs in. The symptom is a good login page, the user logs in then all links and progress fail after that initial login.
The network admin says:
I have done some additional testing on this site and this attachment is a trace of the transaction to (our forums)from a (company network) logged in as (username). If you notice the line that says: Cache-Control: no-cache. This means that your site is not being cached on the proxy.
With that being said, if I leave the site open on my test box, I see that the site is constantly updating or checking in with your server. This check-in happens every 30 seconds. This happens even if I don’t click on any links. If I leave the session open for an extended time an authentication box pops up. If I simply close the box the (forums) site continues working. If I re-login to the proxy, the site quits responding to any requests. When I close out the browser window and re-open it and login, the site goes on working like it should. I wonder if the cookie is being expired or breaking. At the end of the log you can see where the authentication begins failing. The time from the first log until the failed authentication is 10 minutes. Is there a setting on the forum to expire an inactive cookie or session after 10 minutes? I did read on your forum that others have been having troubles related to cookies.
Any ideas from you gurus? I am at a loss. Thanks.
