Why should be the css not cached?
Where do you put the code you are mentioning? Because request that
fetches css (and other resources) is different than request for a page /
ajax request and wicket treats it differently.
What's the reason of not caching css?
-Matej
Carfield Yim wrote:
> look like there is strangle browser cache for ajax component
> (modalwindow is the one I get this problem) . Even if I setup HTTP to
> no-cache:
>
> response.setHeader("Pragma", "no-cache");
> response.setHeader("Cache-Control", "no-cache");
> //response.setHeader("Cache-Control", "private");
> response.setDateHeader("Expires", 0);
>
> And most of the content refresh nicely. However, the CSS that
> modalwindow referencing is still in cache. Not sure anyone have the
> problem before?
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
--
get professional wicket training and consultation
http://www.wicket-support.com
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
