#19200: cached_db backend doesn't honor expiry time
----------------------------------+--------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: contrib.sessions | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by aaugustin):
This will be easy to fix for cached_db, and very hard for signed_cookies.
Signed cookies store the date of the signature, and the verification
function takes a maximum age. Unfortunately, the maximum age is known when
the cookie is signed, not when it's verified. Fixing this problem for
signed cookies requires a redesign of the way session expiration is
handled, which is covered by #19201.
I'm updating the title to restrict this ticket to cached_db.
--
Ticket URL: <https://code.djangoproject.com/ticket/19200#comment:1>
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 https://groups.google.com/groups/opt_out.
