-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[HttpKernel] Add a noStore
argument to the #
attribute
#59301
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree 8000 to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
noStore
argument to the #[Cache]
attributenoStore
argument to the #
attribute
noStore
argument to the #
attributenoStore
argument to the #[Cache]
attribute
GromNaN
reviewed
Dec 27, 2024
src/Symfony/Component/HttpKernel/Tests/EventListener/CacheAttributeListenerTest.php
Outdated
Show resolved
Hide resolved
chalasr
reviewed
Dec 27, 2024
src/Symfony/Component/HttpKernel/EventListener/CacheAttributeListener.php
Show resolved
Hide resolved
chalasr
approved these changes
Dec 29, 2024
noStore
argument to the #[Cache]
attributenoStore
argument to the #
attribute
I expected a hotter debate on this to be honest.... 😅 (not that i want a debate) |
GromNaN
approved these changes
Dec 29, 2024
fabpot
approved these changes
Jan 2, 2025
Thank you @smnandre. |
noStore
argument to the #
attributenoStore
argument to the #[Cache]
attribute
noStore
argument to the #[Cache]
attributenoStore
argument to the #
attribute
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a
noStore
argument to the#[Cache]
attribute, allowing controllers to easily set the no-store directive.When set to
true
, it also supersedes thepublic
/private
value.I recently encountered issues with the back-forward cache (bfcache), a browser feature that stores entire pages in memory to make navigating back and forth faster. It can cause problems when pages rely on JavaScript initialization, dynamic content, or state-changing resources. For example, an edit form might reappear after submission just by hitting “Back” (even after a redirection), with no HTTP request being triggered—leading to unexpected behavior and frustrating the user.
Standard cache headers like
Cache-Control: no-cache
don’t stop this behavior. The only reliable way to disable the bfcache across all major browsers is by using theno-store
directive.The HTTP cache documentation states that all options available for the
Response::setCache()
method can also be used with the#[Cache]
attribute. However, theno-store
option is currently missing.Note
This is a very "raw" implementation.. not sure about it or potential consequences I might not have considered... but I wanted to start the discussion :)
Resources: