#29203: Cached Session may cause losing a session, when it failed to connect to
cache backend
-------------------------------------+-------------------------------------
Reporter: Kenial Sookyum Lee | Owner: nobody
Type: Bug | Status: new
Component: contrib.sessions | Version: 1.11
Severity: Normal | Resolution:
Keywords: session cookie, | Triage Stage:
cached session | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* has_patch: 1 => 0
Comment:
I'm not sure if this is something that Django should implement. The patch
doesn't look elegant because it's adding an implementation detail
(`cache_key`) of a couple of the backends to code that's designed for all
backends.
As far as I know, Django generally [https://github.com/jazzband/django-
constance/issues/236#issuecomment-346974084) requires the cache to be
available]. It might be that we should document this requirement and
discourage use of the "ignore connection timeout exception" option that
you mentioned.
--
Ticket URL: <https://code.djangoproject.com/ticket/29203#comment:9>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.f28e253961d043fc9bb2d804de62ee31%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
