Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#31864 closed Bug (fixed)

Session data cannot be decoded during the transition to Django 3.1.

Reported by: Mariusz Felisiak Owned by: Mariusz Felisiak
Component: contrib.sessions Version: 3.1
Severity: Release blocker Keywords:
Cc: Markus Holtermann, Florian Apolloner, Carlton Gibson, אורי Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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).

Change History (6)

comment:1 by Mariusz Felisiak, 4 years ago

Cc: Markus Holtermann Florian Apolloner Carlton Gibson אורי added
Has patch: set

​PR

comment:2 by Carlton Gibson, 4 years ago

Triage Stage: Unreviewed → Accepted

comment:3 by GitHub <noreply@…>, 4 years ago

Resolution: → fixed
Status: assigned → closed

In 99abfe8:

Fixed #31864 -- Fixed encoding session data during transition to Django 3.1.

Thanks אורי for the report.

comment:4 by Mariusz Felisiak <felisiak.mariusz@…>, 4 years ago

In c21bbe08:

[3.1.x] Fixed #31864 -- Fixed encoding session data during transition to Django 3.1.

Thanks אורי for the report.
Backport of 99abfe8f4d3caebcd73548f5bf9e4755bdfed318 from master

comment:5 by Carlton Gibson <carlton@…>, 4 years ago

In b2b0711b:

Refs #31864 -- Doc'd that DEFAULT_HASHING_ALGORITHM requires 3.1.1+ in release notes.

comment:6 by Carlton Gibson <carlton.gibson@…>, 4 years ago

In cdfdbb34:

[3.1.x] Refs #31864 -- Doc'd that DEFAULT_HASHING_ALGORITHM requires 3.1.1+ in release notes.

Backport of b2b0711b555fa292751763c2df4fe577c396f265 from master

Note: See TracTickets for help on using tickets.
Back to Top