Hi Nathan, I used to stick the original request into the session then redirect on successful login. That method does work.
After reading Freddy's book I decided his method was better because it doesn't rely on the session. Following Tim's lead I've been trying to use session variables as little as possible. Doing so prevents problems that occur if the session times out. If you're worried about the user seeing the original request and monkeying with it you can add @Validate(encrypted=true) to the variable that holds the original request. Aaron Nathan Maves wrote: > I have a authentication inteceptor based on the one from the stripes > book. I want a way to forward onto the original action that was > requested once the login is complete. Is there a slick way with > stripes to get this done or am I stuck with splicing together the > requested URI + query string and passing it to the Login action and > then redirecting. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's challenge > Build the coolest Linux based applications with Moblin SDK & win great prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Stripes-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/stripes-users > > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Stripes-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/stripes-users
