![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
Changes between Initial Version and Version 6 of Ticket #63636
- Timestamp:
- 07/14/2025 10:45:44 PM (12 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #63636
- Property Keywords has-patch dev-feedback needs-unit-tests added
- Property Status assigned → accepted
-
Ticket #63636 – Description
initial v6 1 In #21938 and #61942 the `no-store` directive was added to responses when `nochache_headers()` is called. This happens with every authenticated response, and it may often be called when serving unauthenticated responses in e-commerce plugins, such as on the cart and checkout pages. This `no-store` directive prevents proxies from caching the response so that it is not erroneously served to other users. This is a good, however `no-store` has a downside: [https://web.dev/articles/bfcache#minimize-no-store it disables back/forward cache (bfcache)]. This means that authenticated users can get a degraded experience since may not experience instant back/forward navigations enabled by the browser's bfcache. Furthermore, the lack of bfcache can result in data loss when data has been entered via a JavaScript-built UI since this state is lost when a page is not restored via bfcache. (See [https://github.com/woocommerce/woocommerce/pull/58445#issuecomment-3014404754 demo video] in WooCommerce .)1 In #21938 and #61942 the `no-store` directive was added to responses when `nochache_headers()` is called. This happens with every authenticated response, and it may often be called when serving unauthenticated responses in e-commerce plugins, such as on the cart and checkout pages. This `no-store` directive prevents proxies from caching the response so that it is not erroneously served to other users. This is a good, however `no-store` has a downside: [https://web.dev/articles/bfcache#minimize-no-store it disables back/forward cache (bfcache)]. This means that authenticated users can get a degraded experience since may not experience instant back/forward navigations enabled by the browser's bfcache. Furthermore, the lack of bfcache can result in data loss when data has been entered via a JavaScript-built UI since this state is lost when a page is not restored via bfcache. (See [https://github.com/woocommerce/woocommerce/pull/58445#issuecomment-3014404754 demo video] in WooCommerce for a `no-store` removal PR which is now merged.) 2 2 3 3 (There are other [https://web.dev/articles/bfcache#optimize reasons] for why bfcache may be disabled for a page. One example is the use of the [https://web.dev/articles/bfcache#never-use-the-unload-event unload event]; this was removed in #55491 in order to enable bfcache, only to realize that `no-store` had been recently added in #21938 so no navigation benefit was gained.)
