diff options
| author | Tim Graham <timograham@gmail.com> | 2016-04-04 11:55:34 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-04-04 11:55:34 -0400 |
| commit | 15a20dc9aff1bd8a055ee7c322631b3ca4d1c474 (patch) | |
| tree | 4cb4f2420e592c764012b16d1bb67d07e6e55f85 | |
| parent | f8b31dfdfc0cf6a516bcbc10c4e2f696ce3a9bda (diff) | |
Removed a reference to Django 1.3.1 in docs.
| -rw-r--r-- | docs/topics/security.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/topics/security.txt b/docs/topics/security.txt index 0707da0473..324e198410 100644 --- a/docs/topics/security.txt +++ b/docs/topics/security.txt @@ -196,9 +196,9 @@ For more details see the full :setting:`ALLOWED_HOSTS` documentation. Django now requires that you set :setting:`ALLOWED_HOSTS` explicitly rather than relying on web server configuration. -Additionally, as of 1.3.1, Django requires you to explicitly enable support for -the ``X-Forwarded-Host`` header (via the :setting:`USE_X_FORWARDED_HOST` -setting) if your configuration requires it. +Additionally, Django requires you to explicitly enable support for the +``X-Forwarded-Host`` header (via the :setting:`USE_X_FORWARDED_HOST` setting) +if your configuration requires it. Session security ================ |