Opened 12 years ago
Closed 12 years ago
#18302 closed Bug (invalid)
1.4 cache session storage is not backward compatible
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Documentation | Version: | 1.4 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
I just updated from 1.3 to 1.4 using
django.contrib.sessions.backends.cache
and my sessions were lost.
Apparently the cache backend in 1.4 uses an
extra prefix to store the session_key in the cache:
KEY_PREFIX = "django.contrib.sessions.cache"
Since this prefix cannot be configured from the
settings, I had to create a new cache session backend
based on the 1.4 version, setting KEY_PREFIX to "".
I cannot find anything about this change in the
changelogs. Did I miss something?
Note:
See TracTickets
for help on using tickets.
It was a change in 1.3.1 - https://docs.djangoproject.com/en/dev/releases/1.3.1/
According to those notes, we didn't consider it backwards incompatible since sessions are meant to be transient. In addition, you shouldn't have been upgrading from 1.3 to 1.4 - you should have been using 1.3.1 as soon as it was released since it was a security release.
For those reasons I'm going to mark INVALID.