# HTTP Reverse Proxy Caching - what to cache?

**URL:** <https://community.developer.atlassian.com/t/http-reverse-proxy-caching-what-to-cache/18929>\
**Category:** Everything Else\
**Tags:** cache, proxy, server, jira-server\
**Created:** [May 24, 2018, 11:03am UTC](https://community.developer.atlassian.com/t/http-reverse-proxy-caching-what-to-cache/18929 "2018-05-24T11:03:11Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon63767636](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@anon63767636](https://community.developer.atlassian.com/u/anon63767636)\
**Post date:** [May 24, 2018, 11:03am UTC](https://community.developer.atlassian.com/t/http-reverse-proxy-caching-what-to-cache/18929/1 "2018-05-24T11:03:11Z")

</div>

Hi folks,

this is a hybrid question between infrastructure-related and application-related topics. I’ve approached Atlassian’s support recently because I wonder which types of content can be cached from an Atlassian application (be it Jira, Confluence, etc.). Next to the FR for some official documentation ([[JRASERVER-67353] Recommendation on HTTP caching - Create and track feature requests for Atlassian products.](https://jira.atlassian.com/browse/JRASERVER-67353) - feel free to also vote if that’s something you’d also want to have) they also recommended to get in touch with the Developer Community.  
The problem is that, as far as I’ve had to learn, there is a lot of stuff you can cache flawlessly (e.g. images or some stylesheets) but also a few things that seem to be static but are dynamic (e.g. batches that are regenerated upon addon installation). Can you guys help me out with sharing your experiences and what I could consider to create a high-performance, but not too error-prone caching setup?

Warm regards  
Peter

---

<div class="post-metadata">

**Author:** ![sopel](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/sopel/32/48679_2.png) [@sopel](https://community.developer.atlassian.com/u/sopel)\
**Post date:** [June 6, 2018, 12:10pm UTC](https://community.developer.atlassian.com/t/http-reverse-proxy-caching-what-to-cache/18929/2 "2018-06-06T12:10:32Z")

</div>

Craig Castle-Mead has thankfully recently summarized his related exploration and promising results in [CDN/CloudFront and Atlassian Server apps](https://community.atlassian.com/t5/Jira-discussions/CDN-CloudFront-and-Atlassian-Server-apps/td-p/731230).

I have yet to implement this for our own production instances due to a complication via an additional auth layer, but his configuration seems to be a good starting point that can probably be further refined over time (for the AWS context, we might try to codify and evolve this configuration as a CloudFormation template, though ideally it should be a feature of Atlassian’s own Data Center quick starts in [atlassian-aws-deployment](https://bitbucket.org/atlassian/atlassian-aws-deployment/) of course).

---

<div class="post-metadata">

**Author:** ![anon63767636](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@anon63767636](https://community.developer.atlassian.com/u/anon63767636)\
**Post date:** [June 13, 2018, 1:59pm UTC](https://community.developer.atlassian.com/t/http-reverse-proxy-caching-what-to-cache/18929/3 "2018-06-13T13:59:12Z")

</div>

Thanks, Steffen. That’s sort of the thing we were looking for. We’ll also evaluate the benefit of these settings but indeed, they look promising.