I have (I am using MixedParamHybridUrlCodingStrategy) however in this case
the browser is not contacting the server on back button click so the
UrlCodingStrategy does not come into play.
Ryan
On Wed, Oct 6, 2010 at 4:13 PM, mzem...@osc.state.ny.us wrote:
I've had similar issues, have you tried
See https://issues.apache.org/jira/browse/WICKET-923 for a solution.
On Mon, 11 Oct 2010 09:31 -0500, Ryan Crumley crum...@gmail.com
wrote:
I have (I am using MixedParamHybridUrlCodingStrategy) however in this
case
the browser is not contacting the server on back button click so the
I've had similar issues, have you tried HybridUrlCodingStrategy?
Notice: This communication, including any attachments, is intended solely
for the use of the individual or entity to which it is addressed. This
communication may contain information that is protected from disclosure
under
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
Yes, it is not repeatable on FF because FF does page caching which IE
does not for Back history.
Your page must be stateless on the server side.
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-mail: cika...@gmail.com
On Sun, Oct 3, 2010 at 3:47 PM, Ryan Crumley crum...@gmail.com wrote:
What
Just to clarify:
The page in the example link I sent is stateless (it's static html). The
other point is that Chrome and IE do not fetch the original page on back
button click. They are serving the original html straight from the cache
(without the DOM modifications).
It sounds like the only fix
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.
--
Take a look at
http://www.richardnichols.net/2010/03/apache-wicket-force-page-reload-to-fix-ajax-back/
On Wed, Sep 22, 2010 at 12:58 PM, Ryan Crumley crum...@gmail.com wrote:
All,
I ran into strange behavior involving wicket ajax updates + chrome + back
button. I am pretty sure the issue is
All,
I ran into strange behavior involving wicket ajax updates + chrome + back
button. I am pretty sure the issue is not caused by wicket but I am hoping
the problem might sound familiar to someone and they can point me in the
right direction. The scenario goes like this:
- An ajax request is
