Symptoms

Interaction with the Jira application is slow.

Cause

Jira pages pull many separate JavaScript, CSS and image files from the server. Since the Tomcat container instructs the browser to avoid caching, all content will be sequentially (in order of inclusion) checked from the server. This multiplies the connection roundtrip time.

The content on this page relates to platforms which are not supported by JIRA. Consequently, Atlassian cannot guarantee providing any support for it. Please be aware that this material is provided for your information only and using it is done so at your own risk.

Workaround

Configuring cache timeouts on the proxy level

If the application is published from a Reverse Proxy, configure cache timeouts as shown in the below example.

1. An example for Apache httpd using mod_expires:

   LoadModule expires_module modules/mod_expires.so
   LoadModule headers_module modules/mod_headers.so
   LoadModule deflate_module modules/mod_deflate.so
   

   Make sure it is enabled

2. Control the caching headers sent to the client browser:

   ExpiresActive On
   ExpiresDefault "access plus 300 seconds"
   
   <Directory "/">
       ExpiresByType text/html "access plus 1 day"
       ExpiresByType text/css "access plus 1 day"
       ExpiresByType text/javascript "access plus 1 day"
       ExpiresByType image/gif "access plus 1 month"
       ExpiresByType image/jpg "access plus 1 month"
       ExpiresByType image/png "access plus 1 month"
   </Directory>
   

Resolution

Configuring caching at the browser level

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