summaryrefslogtreecommitdiff
path: root/docs/topics
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2014-07-09 13:54:41 -0400
committerTim Graham <timograham@gmail.com>2014-07-09 14:12:32 -0400
commita3d710a38f1fab5e092cef7a17826674a00e70ea (patch)
tree4ecb76cb4ebaa5d23546b4b9814022718cf36f75 /docs/topics
parent9673013abe4cd64183bf55d89adfa04927e3b947 (diff)
[1.7.x] 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. Backport of 3a85aae2ea from master
Diffstat (limited to 'docs/topics')
-rw-r--r--docs/topics/http/sessions.txt7
1 files changed, 0 insertions, 7 deletions
diff --git a/docs/topics/http/sessions.txt b/docs/topics/http/sessions.txt
index 5711b0c490..8367d582ea 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.