Switching from cookie-based sessions to memcached-based sessions raises exception
|Reported by:||Gabriel Hurley||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
When using the cookie-based session backend, the entire session cookie is stuffed into the session name. If you then switch the session backend to a backend with a length limit (such as memcached, or some DBs) you'll get very obtuse errors such as "Key too long" from memcached.
While arbitrarily switching session backends isn't generally supported behavior, this could be a huge problem for a production site if they ever decided cookie-based sessions weren't ideal for their uses and switched. It would immediately break for every user who had an existing session on the site.
Ideally, if the session backend is unable to retrieve the session due to an error during retrieval, a new session should be generated.
Change History (10)
comment:1 Changed 5 years ago by
|Triage Stage:||Unreviewed → Accepted|
|Version:||1.3 → 1.4-beta-1|