Browser Caching of Static Resources

, ,
1

I’ve searched around in here all morning, and can’t seem to find anything that addresses this question.

I’m writing some DSP pages as a quick way to support some back-end functionality. I’m using jquery and style sheets. It appears that everything served up out of pub has the no-cache directives set fro the browser, so all of this garbage gets re-requested. I’ve been trying to find a way to control this. It seems unreasonable to me that no-cache would be set on static content.

It seems that all of the DSP apps in IS are getting this no-cache treatment (like WmRoot). I checked MWS, and it is more sane. It does allow the browser to cache things.

So I guess I have two questions:

  1. Is there a way to configure IS or write something to let static resources served up by IS get cached?
  2. If not, what do you do? Is this an actual reason to use tomcat in IS? I was hoping to avoid that.

Thanks.
Jason

2

  1. Is there a way to configure IS or write something to let static resources served up by IS get cached?
    What do you mean “static resources”? For customized service, there is a property “Cache result” could be used to cache service execution result. For customized DSP page, you could remove the meta info Pragma: no-cache from the source.

  2. If not, what do you do? Is this an actual reason to use tomcat in IS? I was hoping to avoid that.
    Tomcat in IS is used as the container of J2EE application via WmTomcat package, if you have no customized JSPs/Servlet, you don’t need to use that.