This feature is only shown in the feature list to users with edit access.

A behavior change to safely store (and restore) pages in the Back/Forward Cache despite the presence of a "Cache-control: no-store" HTTP header on HTTPS pages.

Motivation

Cache-control: no-store is an HTTP header to indicate that caches should refrain from storing the response sent by a server. Despite the name, Back/Forward Cache (or BFCache) is not a cache in the HTTP sense, and this behavior does not apply in theory. Indeed, BFCache does not store web resources (HTTP responses) for later use, like an HTTP cache would. Instead, a BFCache is freezing previous web pages in memory, and restoring them when a user navigates back, or forward. In practice, all the current BFCache implementations have been treating Cache-control: no-store as a signal to not keep the associated web pages. This has been going for a while, and the web ecosystem has built an expectation around this particular behavior. We have a proposal to make BFCache work despite the presence of Cache-control: no-store on HTTPS pages, thereby significantly increasing the fraction of instant back/forward navigations. More details to follow.

Documentation

Specification

Specification link


Specification currently under development in a Working Group

Status in Chromium

Blink


Proposed (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

Owners

Intent to Prototype url

Intent to Prototype thread

Search tags

bfcache,

Last updated on 2022-05-10