You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* If the user is not logged in, remove the `no-store` directive so that bfcache is not blocked for visitors,
77
+
* allowing them to benefit from instant back/forward navigations in the storefront. This essentially undoes
78
+
* <https://core.trac.wordpress.org/ticket/61942> which seems to have been excessive since the `private`
79
+
* directive was already being sent to prevent the page from being cached in a proxy server.
80
+
*
81
+
* Note that <https://core.trac.wordpress.org/ticket/63636> proposes removing `no-store` for logged-in users as
82
+
* well. When that happens, the following if statement can be removed since core would no longer be sending
83
+
* `no-store` in the first place.
84
+
*
85
+
* If a site really wants to enforce the `no-store` directive for some reason, they can do so by making sure
86
+
* that the `no-store` directive is added to the `Cache-Control` header via the `wp_headers` filter, for
87
+
* example:
88
+
*
89
+
* add_filter( 'wp_headers', function ( $headers ) {
0 commit comments