#14093: Confusing error when failing to create a session key because the cache
is
unavailable
-------------------------------------+-------------------------------------
Reporter: szymon@… | Owner: nobody
Type: Bug | Status: new
Component: contrib.sessions | Version: 1.2
Severity: Normal | Resolution:
Keywords: session, cache, | Triage Stage: Accepted
session key | Needs documentation: 0
Has patch: 0 | Patch needs improvement: 0
Needs tests: 0 | UI/UX: 0
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* easy: 0 => 1
Comment:
I'm updating the the summary to reflect the fact that this problem isn't
related to load.
Django can't do much if the cache doesn't work, or if the network loses
enough packets to make the cache unusable.
On the other hand, Django should provide a more informative error message
when this situation occurs. This is easy.
--
Ticket URL: <https://code.djangoproject.com/ticket/14093#comment:16>
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 post to this group, send email to django-updates@googlegroups.com.
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
