This has been discussed before (of course) and this is on purpose. If
you reload old pages your users will probably wonder what's going on
(they are not used to this behavior), and secondly there is a
performance hit with no business benefit.
However, you should feel free to change these defaults (by overriding
setHeaders) for cases where another setting is more appropriate.
Regards,
Erik.
kellerautomat wrote:
btw, gere is an interesting point, where IE and Firefox differ from each
other. If you click the back-button of Firefox the page does not reload but
is loaded from cache.
http://blog.httpwatch.com/2008/10/15/two-important-differences-between-firefox-and-ie-caching/
maybe cache-control should be changed to: "Cache-Control: no-cache,
no-store, max-age=0, must-revalidate"
in org.apache.wicket.markup.html.WebPage.setHeaders(WebResponse)
should i open a JIRA?
--
Send from my SMTP compliant software
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
