#23764: sessions.backends.cache.SessionStore does not respect
settings.SESSION_SERIALIZER
--------------------------------------+------------------------------------
Reporter: coagulant | Owner: r4vi
Type: Cleanup/optimization | Status: assigned
Component: contrib.sessions | Version: 1.7
Severity: Normal | Resolution:
Keywords: pickle json sessions | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by erikr):
I would agree with manfre that this should be consistent, and therefore be
fixed. However, it would be worth looking into the commit and ticket that
added this setting and modified the other backends, to see whether this
was perhaps intentional for some special reason.
This would be a backwards incompatible change as well: if users are
running sessions with the cache backend and have not explicitly set
`SESSION_SERIALIZER` to `PickleSerializer`, upgrading will cause all
sessions to be invalidated. (The default value of that setting is
`JSONSerializer`.) Despite that, I still think this change is worth
making, though it will have to be included in the release notes for 1.9.
--
Ticket URL: <https://code.djangoproject.com/ticket/23764#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.2acd7da4cd6cacb24cbd814452509357%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
