WebSphere Commerce - ReLogonFormView / 会话过期如何工作？
抱歉话题太宽泛。基本上，WSC 应该通过将用户转发到 ReLogonFormView 来进行开箱即用的会话超时处理，用户可以将其配置（通过 Struts）到他们选择的任何 jsp。我们使用自定义注销命令，它似乎会影响该视图的显示。
我不是在寻找这个问题的具体解决方案，我只是在寻找有关 WSC (v6) 如何处理会话超时（它如何确定会话已超时）以及它运行的命令的一般知识默认当/if/时判断session已经过期。
Sorry for the broad topic. Basically, WSC is supposed to have out-of-the-box session timeout handling by forwarding the user to the ReLogonFormView, which the user can presumably configure (through Struts) to any jsp that they choose. We use a custom logoff command, and it seems to be affecting that view showing up.
I'm not looking for a specific solution to this problem, I'm just looking for general knowledge about how WSC (v6) handles session timeouts (how it determines that the session has timed out) and what command(s) it runs by default when / if / to determine the session has expired.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
这是我目前对此主题的了解...
会话超时是所有 Web 模块的全局值，可以在 wc-server.xml 中找到，并设置为 30 分钟 OOTB。
发生超时时，通常会调用 OOTB LogoffCmd，它将设置必要的 URL 来导航到 ReLogonFormView URL，同时保留发生会话超时的 URL。
如果 ReLogonFormView 包含允许用户再次登录的用户 ID/密码字段，则用户将被重定向回最初所在的页面。
更多信息可以在 IBM InfoCenter 的“LoginTimeout”下找到。
如果扩展 OOTB LogonCmdImpl，则不应尝试设置转发 URL，否则会干扰 OOTB 导航。
我认为您应该执行自定义注销功能，然后调用 super.performExecute() 以允许 OOTB 导航逻辑接管。
注意：您可以通过调用 getReferrerURL() 检索最初所在的 URL，并且应从 getURL() 返回 ReLogonFormView。
This is my current knowledge on this subject...
The session timeout is a global value for all web modules and can be found in the wc-server.xml and is set to 30 minutes OOTB.
When a timout occurs, the OOTB LogoffCmd would normally be called, which will set up the necessary URLs to navigate to the ReLogonFormView URL while keeping hold of the URL where the session timeout occurred.
If the ReLogonFormView contains userid/password fields to allow the user to logon again, the user will then be redirected back to the page they were originally on.
More info can be found in IBM InfoCenter under "LoginTimeout".
If you extend the OOTB LogonCmdImpl, you should not try and set the forwarding URL, or that will interfere with the OOTB navigation.
I think you should perform your custom logoff functionality and then call super.performExecute() to allow the OOTB navigation logic to take over.
Note: You can retrieve the URL you were originally on via a call to getReferrerURL() and the ReLogonFormView should be returned from getURL().