[1.5.x] Fixed #19962 - Added a note about SESSION_EXPIRE_AT_BROWSER_CLOSE and browsers that persist sessions.

Thanks David Sanders.

Backport of fe5d9fe5fe from master
This commit is contained in:
Tim Graham 2013-03-02 10:11:23 -05:00
parent d43dfdf4b9
commit 142728277a
1 changed files with 10 additions and 0 deletions

View File

@ -474,6 +474,16 @@ This setting is a global default and can be overwritten at a per-session level
by explicitly calling the :meth:`~backends.base.SessionBase.set_expiry` method by explicitly calling the :meth:`~backends.base.SessionBase.set_expiry` method
of ``request.session`` as described above in `using sessions in views`_. of ``request.session`` as described above in `using sessions in views`_.
.. note::
Some browsers (Chrome, for example) provide settings that allow users to
continue browsing sessions after closing and re-opening the browser. In
some cases, this can interfere with the
:setting:`SESSION_EXPIRE_AT_BROWSER_CLOSE` setting and prevent sessions
from expiring on browser close. Please be aware of this while testing
Django applications which have the
:setting:`SESSION_EXPIRE_AT_BROWSER_CLOSE` setting enabled.
Clearing the session store Clearing the session store
========================== ==========================