From de11488c52956d3746f56e71208afe3afa34ca99 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Tue, 2 Apr 2019 09:10:11 +0200 Subject: [PATCH] [2.2.x] Fixed typo in docs/ref/settings.txt. Backport of 4cbe2b06ce580423c62b6e49969f7e24d57d63b8 from master --- docs/ref/settings.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt index 399ffb6a77..e29093dc3a 100644 --- a/docs/ref/settings.txt +++ b/docs/ref/settings.txt @@ -388,7 +388,7 @@ See :setting:`SESSION_COOKIE_SAMESITE` for details about ``SameSite``. Default: ``False`` Whether to use a secure cookie for the CSRF cookie. If this is set to ``True``, -the cookie will be marked as "secure," which means browsers may ensure that the +the cookie will be marked as "secure", which means browsers may ensure that the cookie is only sent with an HTTPS connection. .. setting:: CSRF_USE_SESSIONS @@ -3093,7 +3093,7 @@ Possible values for the setting are: Default: ``False`` Whether to use a secure cookie for the session cookie. If this is set to -``True``, the cookie will be marked as "secure," which means browsers may +``True``, the cookie will be marked as "secure", which means browsers may ensure that the cookie is only sent under an HTTPS connection. Leaving this setting off isn't a good idea because an attacker could capture an