What is interesting is this is not a wicket specific issue however it is more serious when using wicket than other frameworks due to the expired links causing errors when they reappear.
I created a very simple version of the problem. Chrome and IE8 exhibits the problem but Firefox and Safari do not: http://www.cupofcrumley.com/chrome-test/Page1.html <http://www.cupofcrumley.com/chrome-test/Page1.html>Ryan On Fri, Sep 24, 2010 at 1:48 AM, Peter Karich <peat...@yahoo.de> wrote: > I had the same problem ... > > Take a look at > > > http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/ > > > > isn't there a better fix? E.g. it seems to me that this 'hack' avoids > client-side js caching (or is this a wrong observation)? > > Regards, > Peter. > > > > > -- > http://jetwick.com twitter search prototype > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >