Timo, Thanks for your reply. But shouldn't the headers I listed disable caching already? Re-pasting below: Here are A's initial response headers: Server Apache-Coyote/1.1 Cache-Control no-cache, max-age=0, must-revalidate Pragma no-cache Content-Type text/html;charset=UTF-8 Content-Language en-US Content-Length 13209
Timo Rantalaiho wrote: > > On Fri, 14 Nov 2008, dukehoops wrote: >> -user clicks browser back button and lands on A without server being hit >> at >> all. >> >> At this point I expected browser to issue GET /A and A's onBeforeRender >> to >> run. is my expectation correct? If not, what is the expected behavior. >> >> The reason for my question, is that I want to prevent user from >> "back"-ing >> to A once on B. So I wanted to use A's onBeforeRender to evaluate state >> and >> redirect someplace else. If my expectation above is incorrect, could >> someone >> suggest a better approach? > > That behaviour depends on the browser caching behaviour. > Some brosers on some settings get page A from their cache, > in which case the server is not being hit. > > You might get it to work by adding non-caching HTTP headers > on page A. > > Best wishes, > Timo > > -- > Timo Rantalaiho > Reaktor Innovations Oy <URL: http://www.ri.fi/ > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > ----- ---------------- Nikita Tovstoles vside.com ---------------- -- View this message in context: http://www.nabble.com/browser-back-button---shouldn%27t-onBeforeRender%28%29-execute--tp20508047p20544691.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
