[
https://issues.apache.org/jira/browse/WICKET-3722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13034046#comment-13034046
]
manthos commented on WICKET-3722:
---------------------------------
perhaps this issue has something to do with WICKET-3470
> Page Expired after session.invalidate() and setResponsePage()
> -------------------------------------------------------------
>
> Key: WICKET-3722
> URL: https://issues.apache.org/jira/browse/WICKET-3722
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 1.5-RC4
> Reporter: manthos
> Attachments: sample.zip
>
>
> With version 1.5-RC4.2 session invalidate and setResponsePage ends up to a
> PageExpired, until 1.5-RC3 this worked fine. I've made a quickstart to
> reproduce:
> - start it with ''maven jetty:run" and goto localhost:8080
> - click on page 'Safe'
> - 'klick' to sign in (now you're logged in as admin)
> - click 'logout' (session gets invalidated and
> setResponsePage(HomePage.class))
> - now clicking any link you get Page Expired
> Same sample with 1.5-RC3 dependency works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
