Send session data instead of session store options. #289
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 are sending session options instead of session data. I really don't
know the reason cause anybody could be interested on this instead of
request session data.
Session options in a Rails application can be something like this:
Which is, in general, static, doesn't depend on the current request and
well, customers can always just see their configuration file.
I'd say the original intention was send session data.
This fix the serializing JSON problem we are having in some cases where there are socket objects
to Redis or other store backends in those session options.