pragma: No-cache

[Henning Tietgens]

Hi,

is there a reason, why all css an js files from JIRA (standalone 5.1.8) are delivered with pragma: No-cache http header? And, could this be configured? I think if the configured cache of one year could be used this could speed up page loading...

I searched the source and all rows setting pragma headers are setting "no-cache" with a lowercase n. Where does this "No-cache" with an uppercase N come from?

Thanks

Henning

[Henning Tietgens · Accepted solution]

This applies to JIRA installations using SSL over Tomcat. Tomcat defaults to submit the pragma:No-cache header for all files if SSL is used. I think this is for security reasons, so that no pages could be modified within the cache?

With adding this line to the conf/context.xml file within the <context> tag, this could be disabled.

<Valve className="org.apache.catalina.authenticator.BasicAuthenticator"
        securePagesWithPragma="false"
    />

Documentation can be found here http://tomcat.apache.org/tomcat-6.0-doc/config/valve.html#Basic_Authenticator_Valve

After this modification, css and js files are cached.

[Timothy]

One reason I know why this is used is to not cache the filter exports (i.e. excel and word).