From a3d710a38f1fab5e092cef7a17826674a00e70ea Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Wed, 9 Jul 2014 13:54:41 -0400 Subject: [PATCH] [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 --- docs/topics/http/sessions.txt | 7 ------- 1 file changed, 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 @@ -119,13 +119,6 @@ To use cookies-based sessions, set the :setting:`SESSION_ENGINE` setting to stored using Django's tools for :doc:`cryptographic signing ` 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