reiern70 opened a new issue, #1582:
URL: https://github.com/apache/wicket/issues/1582
. SignOut's constructor calls getSession().invalidate() — Wicket only flags
invalidation at this point; the page still renders normally and gets a stateful
page-id for its URL (e.g. SignOut?4).
2. At the very end of that request, Session.endRequest() sees the flag and
calls invalidateNow(), which clears the page store — wiping out the page
instance it just stored under that id.
3. The next request to that now-dangling SignOut?4 URL finds nothing in
the store, falls back to re-constructing the page fresh at the bare SignOut URL
— which repeats the exact same cycle (new session, new id, wiped again)
forever.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
