Re: [jira] Created: (WICKET-1295) partial ajax updates on back button

[Johan Compagner <jc...@gmail.com>]

Set the nostore header of a page, see WebPage.configureResponse()

No store is diabled by default because then nothing is cached and the
backbutton will always generate a call to the server to refresh the
page.

On 1/18/08, Jonathan Locke (JIRA) <ji...@apache.org> wrote:
> partial ajax updates on back button
> -----------------------------------
>
>                  Key: WICKET-1295
>                  URL: https://issues.apache.org/jira/browse/WICKET-1295
>              Project: Wicket
>           Issue Type: Improvement
>           Components: wicket
>     Affects Versions: 1.3.0-final
>             Reporter: Jonathan Locke
>              Fix For: 1.3.1
>
>
> have seen now several times on the web partial ajax updates that occur when
> you press the back button.  most recently, i'm pretty sure this happened on
> the sun download site after finishing a download and then pushing back.  if
> it's not my imagination and this is possible somehow, we should really look
> into this as it's a great feature for something like the cheesr demo in
> wicket in action.  as you go back, you expect the cart to stay current as it
> is really stored in the session not the page.  on an ecommerce site, the
> current workaround would be to refresh the entire page on back every time.
> this would be prohibitively expensive for a company like amazon (who we'd
> like to see adopt wicket one day ;-)).
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
>