django1/django/contrib/sessions/backends
Matt Robenolt 393c0e2422 Fixed #20936 -- When logging out/ending a session, don't create a new, empty session.
Previously, when logging out, the existing session was overwritten by a
new sessionid instead of deleting the session altogether.

This behavior added overhead by creating a new session record in
whichever backend was in use: db, cache, etc.

This extra session is unnecessary at the time since no session data is
meant to be preserved when explicitly logging out.
2014-05-11 21:42:26 -03:00
..
__init__.py Fixed #2066: session data can now be stored in the cache or on the filesystem. This should be fully backwards-compatible (the database cache store is still the default). A big thanks to John D'Agostino for the bulk of this code. 2007-09-15 21:29:14 +00:00
base.py Fixed #20936 -- When logging out/ending a session, don't create a new, empty session. 2014-05-11 21:42:26 -03:00
cache.py Fixed #21012 -- New API to access cache backends. 2013-11-23 15:06:59 +01:00
cached_db.py Fixed #20936 -- When logging out/ending a session, don't create a new, empty session. 2014-05-11 21:42:26 -03:00
db.py More attacking E302 violators 2013-11-02 13:12:09 -07:00
file.py More attacking E302 violators 2013-11-02 13:12:09 -07:00
signed_cookies.py Fixed #20922 -- Allowed customizing the serializer used by contrib.sessions 2013-08-22 13:58:26 -04:00