... -proxy connecting via HTTPS ¶ When deployed behind a reverse-proxy connecting to Django via HTTPS, django.http.HttpRequest.scheme would incorrectly detect client requests made via HTTP as using HTTPS. This entails incorrect results for is_secure() , an ... olute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_SSL_HEADER , if it is configured, and the appropriate header is set on the request, for both HTT ... ts, 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 . 目次 Django 1.11.22 リリースノート CVE-2019-12781: Incorr ... ... xy connecting via HTTPS ¶ When deployed behind a reverse-proxy connecting to Django via HTTPS, django.http.HttpRequest.scheme would incorrectly detect client requests made via HTTP as using HTTPS. This entails incorrect results for is_secure() , an ... olute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_SSL_HEADER , if it is configured, and the appropriate header is set on the request, for both HTT ... ts, 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 . 目次 Django 2.1.10 リリースノート CVE-2019-12781: Incorre ... ... -proxy connecting via HTTPS ¶ When deployed behind a reverse-proxy connecting to Django via HTTPS, django.http.HttpRequest.scheme would incorrectly detect client requests made via HTTP as using HTTPS. This entails incorrect results for is_secure() , an ... olute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_SSL_HEADER , if it is configured, and the appropriate header is set on the request, for both HTT ... ts, 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 . 目次 Django 1.11.22 リリースノート CVE-2019-12781: Incorr ... ... xy connecting via HTTPS ¶ When deployed behind a reverse-proxy connecting to Django via HTTPS, django.http.HttpRequest.scheme would incorrectly detect client requests made via HTTP as using HTTPS. This entails incorrect results for is_secure() , an ... olute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_SSL_HEADER , if it is configured, and the appropriate header is set on the request, for both HTT ... ts, 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 . 目次 Django 2.1.10 リリースノート CVE-2019-12781: Incorre ... ... -proxy connecting via HTTPS ¶ When deployed behind a reverse-proxy connecting to Django via HTTPS, django.http.HttpRequest.scheme would incorrectly detect client requests made via HTTP as using HTTPS. This entails incorrect results for is_secure() , an ... olute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_SSL_HEADER , if it is configured, and the appropriate header is set on the request, for both HTT ... ts, 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 . バグ修正 ¶ Fixed a regression in Django 2.2 where Avg , S ... ... -proxy connecting via HTTPS ¶ When deployed behind a reverse-proxy connecting to Django via HTTPS, django.http.HttpRequest.scheme would incorrectly detect client requests made via HTTP as using HTTPS. This entails incorrect results for is_secure() , an ... olute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_SSL_HEADER , if it is configured, and the appropriate header is set on the request, for both HTT ... ts, 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 . バグ修正 ¶ Fixed a regression in Django 2.2 where Avg , S ... ... dget rendering when option values are tuples ( #28502 ). Django 1.11 inadvertently changed the sequence and trigger naming scheme on Oracle. This causes errors on INSERTs for some tables if 'use_returning_into': False is in the OPTIONS part of DATABASE ... S . The pre-1.11 naming scheme is now restored. Unfortunately, it necessarily requires an update to Oracle tables created with Django 1.11.[1-4]. Use the ... upgrade script in #28451 comment 8 to update sequence and trigger names to use the pre-1.11 naming scheme. Added POST request support to LogoutView , for equivalence with the function-based logout() view ( #28513 ). Omitted page ... ... dget rendering when option values are tuples ( #28502 ). Django 1.11 inadvertently changed the sequence and trigger naming scheme on Oracle. This causes errors on INSERTs for some tables if 'use_returning_into': False is in the OPTIONS part of DATABASE ... S . The pre-1.11 naming scheme is now restored. Unfortunately, it necessarily requires an update to Oracle tables created with Django 1.11.[1-4]. Use the ... upgrade script in #28451 comment 8 to update sequence and trigger names to use the pre-1.11 naming scheme. Added POST request support to LogoutView , for equivalence with the function-based logout() view ( #28513 ). Omitted page ... ... malization on Windows ¶ The URLField form field's to_python() method used urlsplit() to determine whether to prepend a URL scheme to the submitted value. On Windows, urlsplit() performs NFKC normalization , which can be disproportionately slow for larg ... e inputs containing certain characters. URLField.to_python() now uses a simplified scheme detection, avoiding Unicode normalization entirely and deferring URL validation to the appropriate layers. As a result, wh ... LField issue severity permissions normalization characters umask security moderate Potential Unicode Windows used urlsplit scheme validation default control according security policy created file system objects process release クイック検索 Last update: ... ... malization on Windows ¶ The URLField form field's to_python() method used urlsplit() to determine whether to prepend a URL scheme to the submitted value. On Windows, urlsplit() performs NFKC normalization , which can be disproportionately slow for larg ... e inputs containing certain characters. URLField.to_python() now uses a simplified scheme detection, avoiding Unicode normalization entirely and deferring URL validation to the appropriate layers. As a result, wh ... y python permissions normalization characters file umask security moderate low Potential via Unicode Windows used urlsplit scheme 関連するページ Django 6.0.3 release notes Django 5.2.12 release notes Django 4.2.28 release notes Django 5.2.11 release no ... 2026年10月08日