Fixing an issue where strategies were applied to incorrect session configurations #489
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.
Also added 'configuration' to the filter params so the filters know which session configuration it is processing.
Basically here's what I was trying to do:
Have a default session that I use for normal things. But then have a long lived cookie session adapter that uses an encrypted data strategy.
I found that my default session was getting encrypted too and causing all types of trouble.
This patch fixes that bug (with a test case). I also added
'configuration'
to the filter params because without it, my filter had no idea which configuration was being filtered.I'm using filters to get the methods to only write to my default configuration unless I specifically name a configuration in the options. By default, Lithium writes, clears, deletes, and checks all session adapters (but only reads from the first named session adapter).