diff options
| author | Adrian Holovaty <adrian@holovaty.com> | 2011-12-30 21:13:53 +0000 |
|---|---|---|
| committer | Adrian Holovaty <adrian@holovaty.com> | 2011-12-30 21:13:53 +0000 |
| commit | 9fe578c212b16752d478e7b1cb73325c3922f7ad (patch) | |
| tree | eb7d36f0ae4d0a9cbbcfe486a1d71eecbfe8e743 | |
| parent | d4f11eb7766286d48800425b9d923ea28f7cdf2e (diff) | |
Added a bit to the 1.4 release notes about the new SECURE_PROXY_SSL_HEADER setting
git-svn-id: http://code.djangoproject.com/svn/django/trunk@17313 bcc190cf-cafb-0310-a4f2-bffc1f526a37
| -rw-r--r-- | docs/releases/1.4.txt | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/releases/1.4.txt b/docs/releases/1.4.txt index 2c9a1963ca..0cb30d633a 100644 --- a/docs/releases/1.4.txt +++ b/docs/releases/1.4.txt @@ -515,6 +515,11 @@ Django 1.4 also includes several smaller improvements worth noting: * The :ttag:`if` template tag now supports ``{% elif %}`` clauses. +* If your Django app is behind a proxy, you might find the new + :setting:`SECURE_PROXY_SSL_HEADER` setting useful. It solves the problem of your + proxy "eating" the fact that a request came in via HTTPS. But only use this + setting if you know what you're doing. + * A new, plain-text, version of the HTTP 500 status code internal error page served when :setting:`DEBUG` is ``True`` is now sent to the client when Django detects that the request has originated in JavaScript code. |