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);
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
I am now put the CSS to classpath, after the CSS the browser don't get
the new one. And this only happen in ModalWindows, normal webpage will
fetch the CSS after it change
On 12/18/06, Matej Knopp [EMAIL PROTECTED] wrote:
Why should be the css not cached?
Where do you put the code you are
There is indeed a good case for not caching css in development mode. It
is a mortal sin in deployment mode.
Erik.
Carfield Yim wrote:
I am now put the CSS to classpath, after the CSS the browser don't get
the new one. And this only happen in ModalWindows, normal webpage will
fetch the
Where do you put the code you are mentioning? Because request that
Forget to mention about this, I put this block of code at
onBeginRequest() of my custom IRequestCycleFactory.newRequestCycle() .
Which, I suppose the CSS put at class will change the HTTP response
header when somebody request it.
On 12/18/06, Erik van Oosten [EMAIL PROTECTED] wrote:
There is indeed a good case for not caching css in development mode. It
is a mortal sin in deployment mode.
Exactly, but look like it is hard to not cache CSS for AJAX request,
and I just double confirmed that for normal webpage, it work
