... 。 あるページがリクエストされたとき、Django はリクエストに関するメタデータを含んだ HttpRequest オブジェクトを生成します。それから Django は HttpRequest をビュー関数の最初の関数として渡し、適切なビューを読み込みます。あ ... らゆるビューは HttpResponse オブジェクトを返す必要があります。 このドキュメントでは、 HttpRequest と HttpResponse オブジェクトの API を説明しています。これは django.http モジュールにて定義されています。 HttpRequest オブジ ... ェクト ¶ class HttpRequest [ソース] ¶ 属性 ¶ 特に記載がない限り、全ての属性は読み取り専用だと考えてください。 HttpRequest. scheme [ソース] ¶ リクエス ... ... 。 あるページがリクエストされたとき、Django はリクエストに関するメタデータを含んだ HttpRequest オブジェクトを生成します。それから Django は HttpRequest をビュー関数の最初の関数として渡し、適切なビューを読み込みます。あ ... らゆるビューは HttpResponse オブジェクトを返す必要があります。 このドキュメントでは、 HttpRequest と HttpResponse オブジェクトの API を説明しています。これは django.http モジュールにて定義されています。 HttpRequest オブジ ... ェクト ¶ class HttpRequest [ソース] ¶ 属性 ¶ 特に記載がない限り、全ての属性は読み取り専用だと考えてください。 HttpRequest. scheme [ソース] ¶ リクエス ... ... impleTemplateResponse のメソッド) (SyndicationFeed のメソッド) (TemplateResponse のメソッド) __iter__() (File のメソッド) (HttpRequest のメソッド) (ModelChoiceIterator のメソッド) (OGRGeometry のメソッド) __len__() (OGRGeometry のメソッド) __setitem__() (ba ... モジュール) abulk_update() (django.db.models.query.QuerySet モジュール) accept_idna (DomainNameValidator の属性) accepts() (HttpRequest のメソッド) AccessMixin (django.contrib.auth.mixins のクラス) acheck_password() (django.contrib.auth.hashers モジュール) ( ... reate() (django.db.models.query.QuerySet モジュール) aupdate_session_auth_hash() (django.contrib.auth モジュール) auser() (HttpRequest のメソッド) auth() (django.contrib.auth.context_processors モジュール) auth_code() (SpatialReference のメソッド) auth_name ... ... impleTemplateResponse のメソッド) (SyndicationFeed のメソッド) (TemplateResponse のメソッド) __iter__() (File のメソッド) (HttpRequest のメソッド) (ModelChoiceIterator のメソッド) (OGRGeometry のメソッド) __len__() (OGRGeometry のメソッド) __setitem__() (ba ... モジュール) abulk_update() (django.db.models.query.QuerySet モジュール) accept_idna (DomainNameValidator の属性) accepts() (HttpRequest のメソッド) AccessMixin (django.contrib.auth.mixins のクラス) acheck_password() (django.contrib.auth.hashers モジュール) ( ... reate() (django.db.models.query.QuerySet モジュール) aupdate_session_auth_hash() (django.contrib.auth モジュール) auser() (HttpRequest のメソッド) auth() (django.contrib.auth.context_processors モジュール) auth_code() (SpatialReference のメソッド) auth_name ... ... -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 ... () , and build_absolute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_S ... 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 ... ... 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 ... () , and build_absolute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_S ... 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 ... ... ble, as was reported to us recently. The Host header parsing in Django 1.3.3 and Django 1.4.1 -- specifically, django.http.HttpRequest.get_host() -- was incorrectly handling username/password information in the header. Thus, for example, the following Host ... rticularly the password-reset mechanism -- to generate and display arbitrary URLs to users. To remedy this, the parsing in HttpRequest.get_host() is being modified; Host headers which contain potentially dangerous content (such as username/password pairs) n ... 3.5 リリースノート 次のトピックへ Django 1.3.3 リリースノート 関連キーワード Host header parsing password parts URLs users HttpRequest host username validsite リリースノート October fourth release series poisoning independent user written applications make ... ... with reverse-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 ... () , and build_absolute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_S ... 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 ... ... -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 ... () , and build_absolute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_S ... 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 ... ... 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 ... () , and build_absolute_uri() , and that HTTP requests would not be redirected to HTTPS in accordance with SECURE_SSL_REDIRECT . HttpRequest.scheme now respects SECURE_PROXY_S ... 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 ... 2026年10月08日