static content, cache control and expires headers

XMLWordPrintable

    • Type: Bug
    • Resolution: Support Request
    • Priority: Medium
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Environment:

      confluence 3.4.3 standalone on Debian 5

      NOTE: This bug report is for Confluence Server. Using Confluence Cloud? See the corresponding bug report.

      When serving static content or other non changing content the headers are Cache-Control and Expires Headers are set

      e.g.

      HTTP/1.1 304 Not Modified.
      Server: Apache-Coyote/1.1.
      Cache-Control: no-cache, must-revalidate.
      Expires: Thu, 01 Jan 1970 00:00:00 GMT.
      X-Confluence-Request-Time: 1305003489597.
      X-Seraph-LoginReason: OK.
      Last-Modified: Tue, 10 May 2011 02:32:37 GMT.
      ETag: "1304994757000".
      Date: Tue, 10 May 2011 04:58:09 GMT.

      This disables caching in any intervening cache.

      We are setting up Apache as a reverse caching proxy but because of those headers it doesn't cache.

              Assignee:
              Unassigned
              Reporter:
              Deleted Account (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: