---
title: "Note di rilascio di Django 2.1.10"
version: 4.1
locale: it
source: https://docs.djangoproject.com/it/4.1/releases/2.1.10/
canonical: https://djangodocs.dev/it/4.1/releases/2.1.10/
---
# Note di rilascio di Django 2.1.10

*1 Luglio 2019*

Django 2.1.10 risolve un problema di sicurezza in 2.1.9.

## CVE-2019-12781: Incorrect HTTP detection with reverse-proxy connecting via HTTPS

When deployed behind a reverse-proxy connecting to Django via HTTPS,
[`django.http.HttpRequest.scheme`](/it/4.1/ref/request-response/#django.http.HttpRequest.scheme) would incorrectly detect client
requests made via HTTP as using HTTPS. This entails incorrect results for
[`is_secure()`](/it/4.1/ref/request-response/#django.http.HttpRequest.is_secure), and
[`build_absolute_uri()`](/it/4.1/ref/request-response/#django.http.HttpRequest.build_absolute_uri), and that HTTP
requests would not be redirected to HTTPS in accordance with
[`SECURE_SSL_REDIRECT`](/it/4.1/ref/settings/#std-setting-SECURE_SSL_REDIRECT).

`HttpRequest.scheme` now respects [`SECURE_PROXY_SSL_HEADER`](/it/4.1/ref/settings/#std-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`.