for every nudge in the right direction.
Thank you,
Andy
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Copying-PageMaps-from-one-session-to-another-tp3571246p3571246.html
Sent from the Users forum mailing list archive at Nabble.com
.nabble.com/Copying-PageMaps-from-one-session-to-another-tp3571246p3571494.html
Sent from the Users forum mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail
that in Wicket? Other than copying PageMaps?
Cheers,
Andy
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Copying-PageMaps-from-one-session-to-another-tp3571246p3571536.html
Sent from the Users forum mailing list archive at Nabble.com
Andy,
...Not only security frameworks can use this, you can do it yourself by
throwing a RestartResponseAtInterceptPage exception.
Josh
To expand on Josh's suggestion,
In your Login link (probably on an abstract page you inherit for other
app pages) you would have an onClick that doesn't just
setResponsePage(YourLoginPage.class), but instead throws the
Restart...exception. That way, when the login completes, it should
come back
the user visited before signing in,
does not exist.
That was the reason why I wanted to start copying PageMaps from one session
to another in the first place.
If there are any other suggestions as how to prevent session fixation with
Wicket, I'd also be glad to follow any leads into that direction
