If I understood you right. You don't wan't the browser to cache previous pages. So when a user is for example viewing his profile page, then clicks on the logout link. A click on the back button doesn't show the users's profile. May be just a message from the browser that this page (the user's profile page) needs to reloaded or something.
I haven't tried anything similar but here is a quick google search: <META Http-Equiv="Cache-Control" Content="no-cache"> <META Http-Equiv="Pragma" Content="no-cache"> <META Http-Equiv="Expires" Content="0"> Source:http://www.pacificnet.net/~johnr/meta.html I think there was a similar and not so old question in the users list. About invalidating your session (user = null;), It's much more reliable to actually invalidate the user's HttpSession object. You do that by injecting tapestry's Request interface and then invalidate it's session. Unless that's what you really need to do. @Inject private Request request; @OnEvent(component = "logout", value = "action") private void logout() { log.info("User logging out."); request.getSession(false).invalidate(); } On Tue, Oct 18, 2011 at 4:30 PM, Olga <baek_o...@list.ru> wrote: > I am noted that with back browser button we can see all page history, but > you > can be logout or was logined with other username. > > How i can catch this event? > > Thanks > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Browser-Back-Button-tp4909542p4913885.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > -- *Regards,* *Muhammad Gelbana Java Developer*
