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?
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG