From fe5d9fe5fec2617b9eb8564df77ba5324834cadc Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Sat, 2 Mar 2013 10:11:23 -0500 Subject: [PATCH] Fixed #19962 - Added a note about SESSION_EXPIRE_AT_BROWSER_CLOSE and browsers that persist sessions. Thanks David Sanders. --- docs/topics/http/sessions.txt | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt index 41ae0cafa9..f21c3a497e 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -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 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 ==========================