Secure and Lazy session changes #8716
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
It's much less useful now, so it was just moved to the reference section
weaverryan
added a commit
that referenced
this pull request
Nov 27, 2017
This PR was squashed before being merged into the 3.4 branch (closes #8716). Discussion ---------- Secure and Lazy session changes Fixes #8562 I believe that, in user-land, the only change is that the `framework.session.use_strict_mode` is deprecated, and that we need to say that session data is no longer written unless the session data actually changed. Commits ------- 3e28070 Removing limit_metadata_writes 0a0bca2 Removing use_strict_mode docs, as this feature is deprecated in 3.4
Merged
xabbuh
added a commit
that referenced
this pull request
Nov 29, 2017
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.
Fixes #8562
I believe that, in user-land, the only change is that the
framework.session.use_strict_modeis deprecated, and that we need to say that session data is no longer written unless the session data actually changed.