diff options
| author | Tim Graham <timograham@gmail.com> | 2016-04-04 11:55:34 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2016-04-04 12:38:35 -0400 |
| commit | 9dc22b4ff68ff162f85b87a8f4addf6c0348dafc (patch) | |
| tree | ced2757ea869fc0a1f6d10b01771942f26138f4e | |
| parent | f8b88f6a6bbfec210c2a87b75d2837cbe57f8e42 (diff) | |
[1.9.x] Removed a reference to Django 1.3.1 in docs.
Backport of 15a20dc9aff1bd8a055ee7c322631b3ca4d1c474 from master
| -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 ================ |