2019-06-20 10:45:38 +02:00
|
|
|
============================
|
|
|
|
|
Django 1.11.22 release notes
|
|
|
|
|
============================
|
|
|
|
|
|
|
|
|
|
*July 1, 2019*
|
|
|
|
|
|
|
|
|
|
Django 1.11.22 fixes a security issue in 1.11.21.
|
2019-06-13 10:57:29 +02:00
|
|
|
|
|
|
|
|
CVE-2019-12781: Incorrect HTTP detection with reverse-proxy connecting via HTTPS
|
|
|
|
|
--------------------------------------------------------------------------------
|
|
|
|
|
|
|
|
|
|
When deployed behind a reverse-proxy connecting to Django via HTTPS,
|
|
|
|
|
:attr:`django.http.HttpRequest.scheme` would incorrectly detect client
|
|
|
|
|
requests made via HTTP as using HTTPS. This entails incorrect results for
|
|
|
|
|
:meth:`~django.http.HttpRequest.is_secure`, and
|
|
|
|
|
:meth:`~django.http.HttpRequest.build_absolute_uri`, and that HTTP
|
|
|
|
|
requests would not be redirected to HTTPS in accordance with
|
|
|
|
|
:setting:`SECURE_SSL_REDIRECT`.
|
|
|
|
|
|
|
|
|
|
``HttpRequest.scheme`` now respects :setting:`SECURE_PROXY_SSL_HEADER`, if it
|
|
|
|
|
is configured, and the appropriate header is set on the request, for both HTTP
|
|
|
|
|
and HTTPS requests.
|
|
|
|
|
|
|
|
|
|
If you deploy Django behind a reverse-proxy that forwards HTTP requests, and
|
|
|
|
|
that connects to Django via HTTPS, be sure to verify that your application
|
|
|
|
|
correctly handles code paths relying on ``scheme``, ``is_secure()``,
|
|
|
|
|
``build_absolute_uri()``, and ``SECURE_SSL_REDIRECT``.
|
