Add Session Cache Limiting section for NativeSessionStorage #4728
Conversation
This file contains 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
This was referenced Jan 1, 2015
|
Wow, yep - pretty subtle. Thanks for the note Steve! |
weaverryan
added a commit
that referenced
this pull request
May 23, 2015
…rage (mrclay) This PR was merged into the 2.3 branch. Discussion ---------- Add Session Cache Limiting section for NativeSessionStorage | Q | A | ------------- | --- | Doc fix? | yes | New docs? | no | Applies to | 2.1+ | Fixed tickets | (none) We're implementing HttpFoundation (by itself) to replace our native session implementation and noticed that NativeSessionStorage [eliminates the global session.cache_limiter value](symfony/symfony@39526df). I understand *why* it must do this, but users should be warned that the default usage prescribed in the manual will cause all pages to be sent with no cache-busting headers. Commits ------- 028038e Add section about setting cache_limiter in NativeSessionStorage
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.
We're implementing HttpFoundation (by itself) to replace our native session implementation and noticed that NativeSessionStorage eliminates the global session.cache_limiter value. I understand why it must do this, but users should be warned that the default usage prescribed in the manual will cause all pages to be sent with no cache-busting headers.