diff options
| author | Tim Graham <timograham@gmail.com> | 2014-07-09 13:54:41 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2014-07-09 13:54:41 -0400 |
| commit | 3a85aae2eacae836e2a92de77615569883b81932 (patch) | |
| tree | 93e8ca9ea71ef7b4d135f6580f1e363317241948 | |
| parent | 5e2c4a4bd1f86962842783e0b42ada7b9c14c247 (diff) | |
Revert "Improve cookie based session backend docs." refs #20418
This reverts commit d9c01da1f8ba3d4e0947fd1d619c8f4a9b013360.
This is poor advice as it breaks the test client login (refs #22934).
We can add a note like this back after refs #22986 is resolved.
| -rw-r--r-- | docs/topics/http/sessions.txt | 7 |
1 files changed, 0 insertions, 7 deletions
diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt index 4188655329..936a3c5f5d 100644 --- a/docs/topics/http/sessions.txt +++ b/docs/topics/http/sessions.txt @@ -121,13 +121,6 @@ and the :setting:`SECRET_KEY` setting. .. note:: - When using cookies-based sessions :mod:`django.contrib.sessions` can be - removed from :setting:`INSTALLED_APPS` setting because data is loaded - from the key itself and not from the database, so there is no need for the - creation and usage of ``django.contrib.sessions.models.Session`` table. - -.. note:: - It's recommended to leave the :setting:`SESSION_COOKIE_HTTPONLY` setting ``True`` to prevent tampering of the stored data from JavaScript. |