Hi, have you tried disabling the page store:
http://maciej-miklas.blogspot.de/2013/09/wicket-6-disable-page-serialization.html You can keep the pageId of the last page in the session and redirect to it if a request to an expired page comes in. Have fun Sven Am 7. Mai 2018 11:26:34 MESZ schrieb christophe <madeleine.christo...@wanadoo.fr>: >Hello > >My question/request is about the back button, or more to the point on >how >Wicket processes it and how the default behavior can ve overridden > >Let me explain the context of my question: >I am developping an application ( a web based patient record managment >design specifically for Africa). >Users (MDs, nurses..) open pages to look up/create or modify patients, >episodes of care, prescriptions.... >I want to prevent any user from accessing (going back to) pages that >were >previosuly displayed. There are many reasons for that. >What I currently do (an I am not too happy about the solution is >1) let wicket redisplay the "previous" page when the user clicks on >the >broser back button >2) one displayed the page sends a message to the back end with its ID >(unique ID generated by the application) >3) if the ID is not the ID of the LAST page, the application redisplays >the >last page (hence, overlaying th eprevious on) > >It creates an awful lot of useless HTML traffic and it is ugly > >Hence my question >Is there any way I can force wicket/my aplication to display the LAST >page >anytime the user clicks on the browser's back button > >Thank you very much > >Christophe Montagne > >-- >Sent from: >http://apache-wicket.1842946.n4.nabble.com/Users-forum-f1842947.html > >--------------------------------------------------------------------- >To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >For additional commands, e-mail: users-h...@wicket.apache.org
