#18194: File-based session never expire
----------------------------------+------------------------------------
Reporter: ej | Owner: PaulM
Type: Bug | Status: new
Component: contrib.sessions | Version: 1.4
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Elvard):
Is it necessary to sign session data for all backends? I would define it
for file-based sessions only. For example, signed-cookie backend cares
about signing itself. I don't see any advantage in signing database data
with TimestampSigner since expiration date is stored along with session
data.
--
Ticket URL: <https://code.djangoproject.com/ticket/18194#comment:7>
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.
