#31864: Session data cannot be decoded during the transition to Django 3.1.
--------------------------------------------+--------------------------
Reporter: felixxm | Owner: felixxm
Type: Bug | Status: assigned
Component: contrib.sessions | Version: 3.1
Severity: Release blocker | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------+--------------------------
In d4fff711d4c97356bd6ba1273d2a5e349326eb5f (#31274) we've changed format
for session data, that's why setting `DEFAULT_HASHING_ALGORITHM` to
`'sha1'` is not enough to support running multiple instances of the same
project during the transition to Django 3.1.
We could use the legacy `encode()` when `DEFAULT_HASHING_ALGORITHM ==
'sha1'` (it's a bit hacky).
--
Ticket URL: <https://code.djangoproject.com/ticket/31864>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/050.bb0609f0df8251c817dcd019133471de%40djangoproject.com.
