override webpage#setheaders() and instead of no-cache set a no-store header. that should force the browser to reload the page on backbutton...
-igor On 11/5/07, Christian Alejandro Marquez Grabia <[EMAIL PROTECTED]> wrote: > I am using Wicket version 1.2.6 > > I have been looking for this or related issues in the list, but couldn't > find any to solve my problem. > > I have a page that show a Tree with many items. These items can be deleted > using a link. When the item is deleted the page is reloaded using > SetResponsePage(). Then if I click the browser's back button, I go to the > previous page in which this item was not deleted, causing an inconsistence > between the tree and the real thing, that will eventually cause an internal > error leading the user to the internal error page. > > Is there a way to tell wicket that if the back button is pressed, to reload > the page fully, i.e. rebuild it, not using cache? > > Thanks in advanced, > Chris > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
