An issue was discovered in Django 1.11 before 1.11.22, 2.1 before 2.1.10, and 2.2 before 2.2.3. An HTTP request is not redirected to HTTPS when the SECUREPROXYSSLHEADER and SECURESSL_REDIRECT settings are used, and the proxy connects to Django via HTTPS. In other words, django.http.HttpRequest.scheme has incorrect behavior when a client uses HTTP.
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "binary_version": "1.8.7-1ubuntu5.9", "binary_name": "python-django" }, { "binary_version": "1.8.7-1ubuntu5.9", "binary_name": "python-django-common" }, { "binary_version": "1.8.7-1ubuntu5.9", "binary_name": "python-django-doc" }, { "binary_version": "1.8.7-1ubuntu5.9", "binary_name": "python3-django" } ] }
{ "availability": "No subscription required", "ubuntu_priority": "medium", "binaries": [ { "binary_version": "1:1.11.11-1ubuntu1.4", "binary_name": "python-django" }, { "binary_version": "1:1.11.11-1ubuntu1.4", "binary_name": "python-django-common" }, { "binary_version": "1:1.11.11-1ubuntu1.4", "binary_name": "python-django-doc" }, { "binary_version": "1:1.11.11-1ubuntu1.4", "binary_name": "python3-django" } ] }