#20936: When logging out/ending a session, don't create a new, empty session
--------------------------------------+-----------------------------------
Reporter: mattrobenolt | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: contrib.sessions | Version: master
Severity: Normal | Keywords: session, logout, auth
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
--------------------------------------+-----------------------------------
Previously, when logging out, the existing session is overwritten by a new
sessionid instead of deleting the session all together.
This behavior adds overhead by creating a new session record in whichever
backend being used, db, cache, etc.
This extra session is unnecessary at the time since no session data is
meant to be preserved when explicitly logging out.
See: https://github.com/django/django/pull/1487
--
Ticket URL: <https://code.djangoproject.com/ticket/20936>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/055.82575d490b74ee9f8087d5f9e1fb7a4a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
