"Session expired" not working in Wicket -


when user of wicket application loses session (e.g. session expires), links on pages seeing, , form submissions, show user startpage. instead, if right result cannot displayed, expect wicket show "session expired" error message.

for example, startpage displays data. enter query search field, , click on submit button. expect see either filtered results, or error (session expired), instead wicket silently creates new session , shows startpage, results without filter. looks bug ("filter doesn't work!").

for example, if go page https://login.firstbird.eu/, delete jsessionid cookie, , click on "forgot password" link, you'd expect "forgot password" page displayed instead startpage displayed again. (i know solved bookmarkable link, there other situations rely on session , page information can't solved bookmarkable link.)

there no serialization errors in log, think wouldn't matter anyway. there still going times when session expires (e.g. timeout), no matter if session , pages serializable or not.

i think first noticed functionality in wicket 1.5; i'm pretty worked in wicket 1.4.

this looks bug in wicket me. wrong? misunderstanding intention of wicket here? or doing wrong?

there setting whether show pageexpiredpage or recreate current page: https://github.com/apache/wicket/blob/2de1284a589f7862133bb2c2166bf8563268d252/wicket-core/src/main/java/org/apache/wicket/settings/ipagesettings.java#l67-l77

most people prefer show fresh instance instead of losing context , find way back. that's why default.


Comments

Popular posts from this blog

google chrome - Developer tools - How to inspect the elements which are added momentarily (by JQuery)? -

angularjs - Showing an empty as first option in select tag -

php - Cloud9 cloud IDE and CakePHP -