I've got some problems with the session of my Wicket web application.
After adding custom error pages to my web application I did some test to see
whether they work as expected.
During the test I encountered some strange behavior. In the web.xml I set
the session timeout to 1 minute
using the following xml.
<session-config>
<session-timeout>1</session-timeout>
</session-config>
For the test I started the web application, and logged into the application
using a test user. Then I waited for several minutes and clicked a link in
the menu to provoke an page expired error to see my custom error page. But
this never happens. After clicking the link the page loads normally and the
user is still logged in.
I expected the following. Clicking the link leads to a page expiration
therefore the custom expiration page would be shown and then when clicking
the link on the expiration page the login page would be shown as the user's
session has ended.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/User-is-still-logged-in-after-session-should-have-been-expired-tp4039285p4039285.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
