p31829507
/
django
mirror of https://github.com/django/django.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

[3.0.x] Fixed typos in docs/ref/settings.txt. 

Backport of 4056558a1c from master
This commit is contained in:
Ben Falk 2019-09-13 14:36:35 -04:00 committed by Mariusz Felisiak
parent 4d72c14baf
commit e0bb9092d1
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ref/settings.txt
View File

@ -323,7 +323,7 @@ protection is safe from cross-subdomain attacks by default - please see the
Default: ``False``
Whether to use ``HttpOnly`` flag on the CSRF cookie. If this is set to
``True``, client-side JavaScript will not to be able to access the CSRF cookie.
``True``, client-side JavaScript will not be able to access the CSRF cookie.
Designating the CSRF cookie as ``HttpOnly`` doesn't offer any practical
protection because CSRF is only to protect against cross-domain attacks. If an
@ -1776,7 +1776,7 @@ deletes the old one.
Default: ``False``
Whether to use ``HttpOnly`` flag on the language cookie. If this is set to
``True``, client-side JavaScript will not to be able to access the language
``True``, client-side JavaScript will not be able to access the language
cookie.
See :setting:`SESSION_COOKIE_HTTPONLY` for details on ``HttpOnly``.
@ -3065,7 +3065,7 @@ This setting also affects cookies set by :mod:`django.contrib.messages`.
Default: ``True``
Whether to use ``HttpOnly`` flag on the session cookie. If this is set to
``True``, client-side JavaScript will not to be able to access the session
``True``, client-side JavaScript will not be able to access the session
cookie.
HttpOnly_ is a flag included in a Set-Cookie HTTP response header. It's part of