Matej Knopp-2 wrote:
>
> What Wicket version are you using? Because for reliable versioning you
> will need 1.3. Also you problem can be browser caching the initial DOM
> tree (not the modified one). So you should force browser to fire http
> request on back button too - adding CacheControl: no-store to other
> CacheControl flags in Page.configureResponse. Also this might not work
> in Opera, as the browser is quite stubborn and tends to cache things
> anyway.
>
> -Matej
>
>
I thought the cache control flags that you have indicated should already be
called/set if the page in question is a WebPage (see
WebPage.configureResponse() )
Do I need to do anything to ensure that this method is called?
- Doug
--
View this message in context:
http://www.nabble.com/Page-state%2C-undo-and-versioning--tf4390362.html#a12603266
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
