I will try these suggestions, but I't is quite frustrating that migrating
such a simple function causes so much problems.
In the meanwhile, I read the improvements in the caching mechanisms of
Wicket 1.5 on
https://cwiki.apache.org/WICKET/caching-in-wicket-15.html
It says:
/Caching is uniformly disabled now by sending the following HTTP response
headers:/
So I tried:
HttpServletResponse response =
(HttpServletResponse)getResponse().getContainerResponse();
response.addHeader("Pragma", "no-cache");
response.addHeader("Cache-Control", "no-cache, no-store");
response.addHeader("Expires", "Thu, 01 Jan 1970 00:00:00 GMT");
at various places.
I also put
((WebResponse) getResponse()).disableCaching();
in the body of the onClick,
But Firefox is still caching like a madman!!
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Migrating-a-ResourceStreamRequestTarget-to-a-ResourceStreamRequestHandler-tp3998969p4017233.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
