pragma: No-cache

Henning Tietgens Community Champion Jul 29, 2013


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?



2 answers

1 accepted

1 vote
Accepted answer
Henning Tietgens Community Champion Jul 30, 2013

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.

&lt;Valve className="org.apache.catalina.authenticator.BasicAuthenticator"

Documentation can be found here

After this modification, css and js files are cached.

0 votes
Timothy Chin Community Champion Jul 30, 2013

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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

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...

2,947 views 19 22
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you