|Hi,
Our client is behind a "Microsoft Internet Security and Acceleration
Server 2003", formerly known as the MS Proxy. They had serious issues
with a wicket application, and everything looked like totally broken.
After a little bit debugging|| I found Wicket does not set any
no-cache-headers to the HTTP-requests, and so the proxies cache all the
pages and refuse to reload them even when using the reload button.
So, we should stick these to somewhere in wicket, but what would be the
best place? There is no need to disable caching on static resources, but
the dynamic pages should not ever be proxied.
response.setHeader("Pragma","no-cache");
response.setHeader("Cache-Control","no-store, no-cache, max-age=0,
must-revalidate");
Pragma is HTTP/1.0, and Cache-Control is HTTP/1.1. It does not really
harm to have these both.
--
Janne Hietamäki
Cemron Ltd
http://www.cemron.com/
|
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
