You need to
before you can comment on or make changes to this bug.
HTTP pages that specify "Cache-control: no-store" should not be cacheable to the page cache. Currently they get cached if other factors don't stop it.
This will make "no-store" work consistently and match other browsers.
On HTTPS pages "Cache-control: no-store" and "Cache-control: no-cache" should prevent caching to the page cache. Otherwise they should be cacheable. Currently HTTPS pages are never allowed in the page cache.
This will make page caching available on HTTPS pages in secure manner, improving performance and user experience.
These changes would make WebKit page cache behave similarly to Firefox3 (https://bugzilla.mozilla.org/show_bug.cgi?id=441751).
Consistency with Firefox is a strong argument - however, the current behavior is by design. To prevent a page from getting into page cache, one can add an onunload handler.
In addition to the bugzilla is their developer document of intended behavior: https://developer.mozilla.org/En/Using_Firefox_1.5_caching
Adding another radar - <rdar://problem/7196487> - which tracks enabling https in the page cache (which seems closely related to this bug)
One use case for the current design is the following scenario:
- web search is performed using an engine that returns results with Cache-control: no-store (a totally reasonable thing to do);
- a user clicks some search result, then goes back.
We should be able to return to search results page without making another request to the server, which is slow, and may give different results.
I agree with Alexey here, for non-https pages.
From a user-experience standpoint, this would be absolutely desirable.
In general, there's been a struggle for browser vendors wanting to make the page cache work for more and more pages, and web developers wanting to opt out of the page cache for application-specific reasons.
I get the impression that "Cache-control: no-cache" was set in stone by mozilla to be "the way to opt out."
From a browser-engineer standpoint, and from the standpoint of someone who uses a web browser heavily, "opting out of the page cache" is the same thing as "opting in to low-performance-with-direct-user impact mode."
Is it important for us to *let* them opt out?
I think that maybe we should use this bug to track the https work. That is, we start letting https pages into the page cache, unless they send no-cache or no-store.
In addition to <rdar://problem/7013921>, the HTTPS specific aspect is also covered by <rdar://problem/7196487>
Cache-Control directives are targeted at HTTP caches, and RFC2616 explicitly states that caches and history lists are separate; see http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.13
In particular, see the note at the end.
I'm concerned that while this text is confusing and indeed not very helpful at the moment, re-defining the semantics of existing cache directives in an ad hoc fashion is going to create more confusion and interoperability problems. In other words, we need to document this better, especially if the way that the directives work is going to change.
The HTTPbis Working Group in the IETF is chartered to revise RFC2616, so this is a good opportunity to do that; for example, we could:
* Rewrite section 13.13 to explicitly define CC: no-store as applying to history lists (which is within HTTPbis' charter), or
* Define one or more new directives to explicitly control history lists (which isn't in HTTPbis' charter, but we can provide a forum for discussion and feedback), or
* Refine the text in other ways.
To make that happen, however, we need browser vendors (you) to actively participate in discussions; ideally, making proposals for text changes.
You can see the current drafts at:
and participate on the list at:
I've raised a HTTPbis ticket regarding this particular issue at:
(I'll leave it up to you to dediced whether to reopen this, open a new bug, etc.)
IETF HTTPbis WG Chair / Part 6 (caching) Editor
Right, RFC2616 as-is clearly does not apply to the page cache.
Since this is a browser behavior the HTML5 specification might be the natural place to standardize it. It already acknowledges the existence of the page cache but does not currently go any further: "This specification does not specify when user agents should discard Document objects and when they should cache them."
Coincidental to the comments in this bug, I just blogged about recent and planned changes in our page cache behavior:
See also Bug 49672.
Updating title to:
"Page cache should allow HTTPS pages taking Cache-control header into account"
We've long ignored Firefox's "cache-control: no-store" disqualification for normal HTTP pages and it hasn't identifiably caused any problems.
But in introducing support for HTTPS it would be prudent to play the conservative part and disqualify both "cache-control: no-store" and "cache-control: no-cache" like they do.
And that's what the patch I'm about to attach does.
Created an attachment (id=126830) [details]
Patch v1 - Fix + layout test