summaryrefslogtreecommitdiff
path: root/docs/ref/settings.txt
diff options
context:
space:
mode:
authorTim Graham <timograham@gmail.com>2017-11-01 10:57:59 -0400
committerGitHub <noreply@github.com>2017-11-01 10:57:59 -0400
commitafd375fc343baa46e61036087bc43b3d096bb0ca (patch)
treee1af42ebe5f7db72f44e5474cc51a0a4a5719385 /docs/ref/settings.txt
parentcbe334918a0a80762249706a15b699714b5dc828 (diff)
Fixed #28741 -- Removed unnecessary leading dot from cross-domain cookie examples.
Diffstat (limited to 'docs/ref/settings.txt')
-rw-r--r--docs/ref/settings.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index 3e171c8d3d..4c1b5eb0d7 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -309,7 +309,7 @@ Default: ``None``
The domain to be used when setting the CSRF cookie. This can be useful for
easily allowing cross-subdomain requests to be excluded from the normal cross
site request forgery protection. It should be set to a string such as
-``".example.com"`` to allow a POST request from a form on one subdomain to be
+``"example.com"`` to allow a POST request from a form on one subdomain to be
accepted by a view served from another subdomain.
Please note that the presence of this setting does not imply that Django's CSRF
@@ -1733,8 +1733,8 @@ The age of the language cookie, in seconds.
Default: ``None``
The domain to use for the language cookie. Set this to a string such as
-``".example.com"`` (note the leading dot!) for cross-domain cookies, or use
-``None`` for a standard domain cookie.
+``"example.com"`` for cross-domain cookies, or use ``None`` for a standard
+domain cookie.
Be cautious when updating this setting on a production site. If you update
this setting to enable cross-domain cookies on a site that previously used
@@ -2958,8 +2958,8 @@ The age of session cookies, in seconds.
Default: ``None``
The domain to use for session cookies. Set this to a string such as
-``".example.com"`` (note the leading dot!) for cross-domain cookies, or use
-``None`` for a standard domain cookie.
+``"example.com"`` for cross-domain cookies, or use ``None`` for a standard
+domain cookie.
Be cautious when updating this setting on a production site. If you update
this setting to enable cross-domain cookies on a site that previously used