#23764: sessions.backends.cache.SessionStore does not respect
settings.SESSION_SERIALIZER
--------------------------------------+----------------------------------
Reporter: coagulant | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.sessions | Version: 1.7
Severity: Normal | Keywords: pickle json sessions
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+----------------------------------
According to [https://docs.djangoproject.com/en/1.6/topics/http/sessions
/#session-serialization Session serialization docs], `SESSION_SERIALIZER`
setting, introduced in 1.5.3, allows to customize how session data is
stored. `JSONSerializer` is used as default since 1.6.
All session backends honor this setting, except for
`sessions.backends.cache.SessionStore`, which still uses pickle as
serialization format (not directly, but via cache backend).
It should be documented that cache store ignores this setting or
SessionStore should be modified to support it.
--
Ticket URL: <https://code.djangoproject.com/ticket/23764>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.7660401690248fd9b9e32a048183a011%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
