Improve cookie based session backend docs.
Note the don't require sessions to be in installed apps.
This commit is contained in:
parent
2d0e36ae37
commit
d9c01da1f8
|
@ -118,6 +118,13 @@ To use cookies-based sessions, set the :setting:`SESSION_ENGINE` setting to
|
||||||
stored using Django's tools for :doc:`cryptographic signing </topics/signing>`
|
stored using Django's tools for :doc:`cryptographic signing </topics/signing>`
|
||||||
and the :setting:`SECRET_KEY` setting.
|
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::
|
.. note::
|
||||||
|
|
||||||
It's recommended to leave the :setting:`SESSION_COOKIE_HTTPONLY` setting
|
It's recommended to leave the :setting:`SESSION_COOKIE_HTTPONLY` setting
|
||||||
|
|
Loading…
Reference in New Issue