summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorClaude Paroz <claude@2xlibre.net>2018-06-10 15:11:39 +0200
committerClaude Paroz <claude@2xlibre.net>2018-06-10 15:12:44 +0200
commit020c51d5016379fe80e2029db200c6b7e05d62c1 (patch)
tree80fabac1068142e46c531f83dc2a88cec55ef527 /docs
parentbdc71f526f890a4ccabbceb3ebf4798b06aa82d6 (diff)
[2.1.x] Prevented unexpected link in settings docs
Backport of e8531cc89c878b6a8867498dab266917fef2bff4 from master.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/settings.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/settings.txt b/docs/ref/settings.txt
index 3647e60663..903356a37a 100644
--- a/docs/ref/settings.txt
+++ b/docs/ref/settings.txt
@@ -2199,7 +2199,7 @@ method.
This takes some explanation. By default, ``is_secure()`` is able to determine
whether a request is secure by looking at whether the requested URL uses
-"https://". This is important for Django's CSRF protection, and may be used
+``https://``. This is important for Django's CSRF protection, and may be used
by your own code or third-party apps.
If your Django app is behind a proxy, though, the proxy may be "swallowing" the