Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-7212

Improve caching of static resources

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Fixed
    • 2.3
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Right now, with static resources, we either have to serve with an Expires: header (which means that if the resource is changed by a plugin modification or an upgrade, browsers won't know), or we have to use Last-Modified/eTag (which means that the browser has to do a request/response round trip for every resource in a page, even if it doesn't need to be served.

      By giving each resource a dynamic URL that changes when the resource changes, and then setting them to expire in the distant future, we can get the best of both worlds.

      Candidates for this technique:

      • CSS stylesheets
      • Javascript files (this could mean we could do away with the combined Javascript servlet!)
      • Plugin downloadable resources

      Attachments

        Issue Links

          Activity

            People

              cmiller@atlassian.com Charles Miller
              cmiller@atlassian.com Charles Miller
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: