#34806: Make cached_db backend resilient to cache backend errors
--------------------------------------------+------------------------
Reporter: Claude Paroz | Owner: nobody
Type: Bug | Status: new
Component: contrib.sessions | Version: dev
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
--------------------------------------------+------------------------
In the case storing the session data in the cache for the `cached_db`
backend is failing, this should not make the whole request crash.
Use case: you add a big content to `messages.success`, bigger than what
your configured cache backend can accept (e.g. obtaining a TooBig error
with memcache). Then every future request from that session will crash.
I would suggest to log the failure instead of letting the cache backend
exception crash the request, and continue with the request, as missing
saving the session data in the cache is not a serious condition, it will
only slow the requests a bit as the database will be hit each time until
the issue is solved.
--
Ticket URL: <https://code.djangoproject.com/ticket/34806>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/0107018a4c62d301-985f0687-0669-4eeb-a87d-db5c775e2ca3-000000%40eu-central-1.amazonses.com.
