[wp-trac] [WordPress Trac] #63636: Enable instant page navigations from browser history via bfcache when sending "nocache" headers
WordPress Trac
noreply at wordpress.org
Fri Jan 23 00:23:00 UTC 2026
#63636: Enable instant page navigations from browser history via bfcache when
sending "nocache" headers
-------------------------------------------------+-------------------------
Reporter: westonruter | Owner:
| westonruter
Type: enhancement | Status: accepted
Priority: normal | Milestone: Future
| Release
Component: Administration | Version: 6.3
Severity: normal | Resolution:
Keywords: has-patch dev-feedback needs-unit- | Focuses:
tests | performance, privacy
-------------------------------------------------+-------------------------
Comment (by kkmuffme):
Sorry for not getting back earlier, I had a really long and thought out
comment, which got lost due to an auto-update...
Anyway, Cloudflare improved/fixed/changed various things in the recent
months, making it much saner - in fact they now essentially strictly
adhere to the standard: https://datatracker.ietf.org/doc/html/rfc7234
Quoting MDN:
>Note that no-cache means "it can be stored but don't reuse before
validating" — so it's not for preventing a response from being stored.
>Clear-Site-Data: "cache"
This won't be possible, since it will clear all subdomains (and the domain
itself), not just the current (sub)domain - not only will this massively
worsen usability (since the whole cache is cleared incl. JS/CSS and media
(!) it will result in significantly more traffic for large blog operators.
While for some pages like frontend cart, checkout,... its fine with no-
cache, private, I think in wp-admin this is not the case - be it editing
products (qty!) or pages.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63636#comment:20>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list