当单个用户注销时，其他用户似乎会丢失 AuthTicket
我们正在运行一个 .NET 2.0 Web 应用程序。 我们的一位客户遇到了一个问题，当两个不同的用户在两台不同的计算机上登录应用程序并且其中一个用户注销时，另一个用户似乎丢失了其 AuthTicket（没有显示任何内容，页面看起来已损坏）。 他们必须注销并重新登录才能继续使用该应用程序。 正如您可以想象的那样，这对他们来说非常令人沮丧，他们希望尽快得到答案。
我们在实验室中重新创建了他们的设置并尝试重现该问题，但我们不能。 此外，这个问题在其他网站上也出现过，但在某个时候已经“自行修复”，尽管似乎没有人能解释如何解决。
对我来说，这似乎是某种配置问题，特别是当我们可以使用相同的硬件运行相同的版本但看不到它时。 然而，到目前为止我所做的测试和研究没有取得任何成果。 唯一半有用的信息是检查应用程序池是否设置为在使用过多内存或其他情况时回收。
有人有主意吗？
如果有帮助的话，这是用于身份验证的 web.config 条目：
<authentication mode="Forms">
<forms name=".EyeQCookie" loginUrl="Login.aspx" protection="All" timeout="30" path="/" slidingExpiration="true">
</forms>
</authentication>
We are running a .NET 2.0 Web Application. One of our clients is experiencing an issue where, when two different users are logged into out application on two different machines and one logs out the other user seems to lose its AuthTicket (none of the content is displayed and the page just looks broken). They must log out and log back in again in order to continue using the application. As you can image, this is very frustrating to them and they want answers ASAP.
We recreated their setup in our lab and attempted to reproduce the issue but we cannot. Also, this issue has been seen on other sites but has "fixed itself" at some point, though no one can seem to explain how.
This seems like some sort of configuration issue to me, especially when we can run the same version with the same hardware and don't see it. However, the testing and research I have done thus far has yielded NOTHING. The only semi useful information was to check to see if the AppPools are set to recycle if using too much memory or something.
Anyone have any ideas?
Here is the web.config entry for authentication if this helps:
<authentication mode="Forms">
<forms name=".EyeQCookie" loginUrl="Login.aspx" protection="All" timeout="30" path="/" slidingExpiration="true">
</forms>
</authentication>
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
AuthTickets 不存在问题，尽管它的行为与事实完全一样。 问题在于缓存以及我们如何使用/存储这些值（更具体地说是剥皮——>我们有点落后于时代）。
The issue was no with AuthTickets, though it was behaving exactly as if it was. The issue was with cache and how we use/store the values (more specifically skinning --> we are a tad behind the times).