#18194: File-based session never expire
----------------------------------+------------------------------------
Reporter: ej | Owner: crodjer
Type: Bug | Status: assigned
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
----------------------------------+------------------------------------
Changes (by crodjer):
* owner: nobody => crodjer
* status: new => assigned
* has_patch: 0 => 1
Comment:
I made some attempts with this in `file-session-server-
expiry-{2,3}.patch`. The 2nd uses files modification time to decide on
expiry. The 3rd uses the signing framework's timed signer for handling the
expiration. Also added a test which is supposed to emulate the ticket
behaviour.
Moreover, `sessions-cleanup-files-1.patch` adds support for cleaning of
file sessions with management cleanup command. It moves the session
backend specific cleanup logic to their own modules and the management
command invokes cleanup command according to the current backend. The base
backend implements a cleanup class method which is supposed to be
overridden by the backends.
--
Ticket URL: <https://code.djangoproject.com/ticket/18194#comment:5>
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.
