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
This commit is contained in:
parent
d4f11eb776
commit
9fe578c212
|
@ -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.
|
||||
|
|
Loading…
Reference in New Issue