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

      The default Wiki pages include in their header:

      <META HTTP-EQUIV="Pragma" CONTENT="no-cache">
      <META HTTP-EQUIV="Expires" CONTENT="-1">

      But Pragma: no-cache and Expires=-1 are HTTP headers defined in HTTP/1.0, not HTTP/1.1. It's not really appropriate for most enterprise deployments, where everyone is running a browser newer than IE 5.

      There is no reason to 'not cache'. You just want to validate the cache. With Pragma: no-cache, some browsers will not let you use the page you already loaded when you hit the 'back' button, and thus reload the page, scroll to the top, throw away any form data that might already be partially filled in.

      It would be better to use HTTP/1.1 constructs; perhaps

      cache-control: max-age=0

      and even better to put that in the HTTP server, rather than sticking it into every HTML page sent over the net.

            [CONFSERVER-7457] Remove meta cache control elements from Confluence HTML

            Hi Guy,

            With the resolution of this issue, Confluence will no longer be sending any <meta http-equiv= ... > elements in the HTML

            Other caching changes for this release are described at CONF-9289 and CONF-9290

            Cheers,
            Chris

            Christopher Owen [Atlassian] added a comment - - edited Hi Guy, With the resolution of this issue, Confluence will no longer be sending any <meta http-equiv= ... > elements in the HTML Other caching changes for this release are described at CONF-9289 and CONF-9290 Cheers, Chris

            Hi,

            Could you provide information on what the headers have been changed to? Our Theme Builder plugin does some messing with the cache headers based on theme settings and we want to ensure compatibility with 2.7.x.

            Guy Fraser [Adaptavist.com] added a comment - Hi, Could you provide information on what the headers have been changed to? Our Theme Builder plugin does some messing with the cache headers based on theme settings and we want to ensure compatibility with 2.7.x.

            temporarily reopening in order to request code review

            Per Fragemann [Atlassian] added a comment - temporarily reopening in order to request code review

            I'm going to look at attacking HTTP caching features for 2.7

            Christopher Owen [Atlassian] added a comment - I'm going to look at attacking HTTP caching features for 2.7

            I would like to see this resolved soon as well, I have just rolled out confluence to much a great many people and while I would not have an issue occassionally having to refresh my search results, many of my collegues are becoming frustrated with this functionality. Is this something that I can easily change within my confluence configruation (perhaps to a template or something) or is this somethingt hat will need to be fixed as a release?

            thanks!

            Richard C. Tallini added a comment - I would like to see this resolved soon as well, I have just rolled out confluence to much a great many people and while I would not have an issue occassionally having to refresh my search results, many of my collegues are becoming frustrated with this functionality. Is this something that I can easily change within my confluence configruation (perhaps to a template or something) or is this somethingt hat will need to be fixed as a release? thanks!

            The handling of the 'Pragma: no-cache / Expires: -1' seems to be different in Internet Explorer when using 'https' vs 'http'. See

            http://support.microsoft.com/default.aspx/kb/234067

            So, sites that don't use SSL might not see as many problems as those that use https (to protect credentials over the Internet).

            From the Microsoft support site:

            "Remember that it is not a good idea to use this header globally across the entire Web server. Restrict its use purely to content that absolutely must not be cached on the client. "

            Larry Masinter added a comment - The handling of the 'Pragma: no-cache / Expires: -1' seems to be different in Internet Explorer when using 'https' vs 'http'. See http://support.microsoft.com/default.aspx/kb/234067 So, sites that don't use SSL might not see as many problems as those that use https (to protect credentials over the Internet). From the Microsoft support site: "Remember that it is not a good idea to use this header globally across the entire Web server. Restrict its use purely to content that absolutely must not be cached on the client. "

            Sorry, this is in version 2.2.6, not 2.3-DR2.
            And 'Major' is probably the wrong priority.

            Larry Masinter added a comment - Sorry, this is in version 2.2.6, not 2.3-DR2. And 'Major' is probably the wrong priority.

              pfragemann Per Fragemann [Atlassian]
              98b1539ce087 Larry Masinter
              Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: