电梯会话到期
我是新手，正在尝试编写一个简单的登录应用程序。当我离开登录页面一段时间并输入用户名和密码时，它不会登录，而是会执行会话过期行为。 我检查了日志，发现每当我收到 INFO - Session navoo0xdu1ia1vi8m1c0cnl3w expired 日志消息时，就会发生上述行为。
我无法理解为什么请求使用现有会话，即使它已经过期。请指导我在哪里可以找到文档/示例/教程来了解此行为以及如何实现基于简单会话的登录功能。
任何帮助将不胜感激，因为这个问题对我来说是瓶颈。我用谷歌搜索了很多，但找不到任何有用的东西。
I am new to lift and trying to write a simple login application. When I leave my login page for some time, and I enter username and password it doesn't login instead it perform session expire behavior.
I checked the log and found that whenever I got INFO - Session navoo0xdu1ia1vi8m1c0cnl3w expired log message, the above behavior happens.
I am not able to understand why request is using the existing session, even if it's already expired. Please guide me where can I found documentation/example/tutorial to understand this behavior and how to implement simple session based login functionality.
Any help will be appreciated since this problem is bottleneck to me. I googled a lot but couldn't find anything useful.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您的会话即将过期，那么这是由于以下两种原因之一：
1) LiftRules.sessionInactivityTimeout 中设置的值
或
2) 容器会话中为会话过期设置的值。
前者实际上默认设置为空，这意味着后者将覆盖它。但请注意，如果您正在与 Lift 交互并且尚未禁用心跳脉冲，则会话不会过期。如果您观察 AJAX 流量，您会注意到用于函数 GC 的页面心跳，它使页面绑定函数保持活动状态。
If your session is expiring then it is because of one of two things:
1) The value set in LiftRules.sessionInactivityTimeout
or
2) The value set for session expiry within your container session.
The former is actually set to nothing by default, which means the latter will override it. Be aware however that provided you are interacting with Lift and have not disabled the heartbeat pulse then sessions do not expire. If you watch the AJAX traffic you will notice a page heartbeat used for function GC which keeps the page bound functions alive.