... endent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host header. Some attacks against this are beyond Django's ability to control, and require the web server to be properly config ... documentation has for some time contained notes advising users on such configuration. Django's own built-in parsing of the Host header is, however, still vulnerable, 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 header wo ... ... endent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host header. Some attacks against this are beyond Django's ability to control, and require the web server to be properly config ... documentation has for some time contained notes advising users on such configuration. Django's own built-in parsing of the Host header is, however, still vulnerable, 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 header wo ... ... endent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host header. Some attacks against this are beyond Django's ability to control, and require the web server to be properly config ... documentation has for some time contained notes advising users on such configuration. Django's own built-in parsing of the Host header is, however, still vulnerable, 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 header wo ... ... endent of end-user-written applications -- make use of full URLs, including domain name, which are generated from the HTTP Host header. Some attacks against this are beyond Django's ability to control, and require the web server to be properly config ... documentation has for some time contained notes advising users on such configuration. Django's own built-in parsing of the Host header is, however, still vulnerable, 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 header wo ... ... is the sixth bugfix/security release in the Django 1.3 series. Host header poisoning ¶ Some parts of Django -- independent of end-user-written applications -- make use of full URLs, includin ... g domain name, which are generated from the HTTP Host header. Django's documentation has for some time contained notes advising users on how to configure web servers to ensure ... that only valid Host headers can reach the Django application. However, it has been reported to us that even with the recommended web server co ... ... l other bugs and numerous documentation improvements. This is the fourth bugfix/security release in the Django 1.4 series. Host header poisoning ¶ Some parts of Django -- independent of end-user-written applications -- make use of full URLs, includin ... g domain name, which are generated from the HTTP Host header. Django's documentation has for some time contained notes advising users on how to configure web servers to ensure ... that only valid Host headers can reach the Django application. However, it has been reported to us that even with the recommended web server co ... ... is the sixth bugfix/security release in the Django 1.3 series. Host header poisoning ¶ Some parts of Django -- independent of end-user-written applications -- make use of full URLs, includin ... g domain name, which are generated from the HTTP Host header. Django's documentation has for some time contained notes advising users on how to configure web servers to ensure ... that only valid Host headers can reach the Django application. However, it has been reported to us that even with the recommended web server co ... ... l other bugs and numerous documentation improvements. This is the fourth bugfix/security release in the Django 1.4 series. Host header poisoning ¶ Some parts of Django -- independent of end-user-written applications -- make use of full URLs, includin ... g domain name, which are generated from the HTTP Host header. Django's documentation has for some time contained notes advising users on how to configure web servers to ensure ... that only valid Host headers can reach the Django application. However, it has been reported to us that even with the recommended web server co ... ... 6.1 で非推奨: The following settings and functions will be removed in Django 2028: EMAIL_BACKEND , EMAIL_FILE_PATH , EMAIL_HOST , EMAIL_HOST_PASSWORD , EMAIL_HOST_USER , EMAIL_PORT , EMAIL_SSL_CERTFILE , EMAIL_SSL_KEYFILE , EMAIL_TIMEOUT , EMAIL_USE_ ... s ... , }, }, } For example, to update these settings: EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" EMAIL_HOST = "mail.example.net" EMAIL_USE_TLS = True EMAIL_PORT = 587 EMAIL_HOST_USER = "user@example.net" EMAIL_HOST_PASSWORD = "pas ... sword" use: MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIONS" : { "host" : "mail.example.net" , "use_tls" : True , # port is not needed: it defaults to 587 with use_tls True. "username" : "user@ ... ... 6.1 で非推奨: The following settings and functions will be removed in Django 2028: EMAIL_BACKEND , EMAIL_FILE_PATH , EMAIL_HOST , EMAIL_HOST_PASSWORD , EMAIL_HOST_USER , EMAIL_PORT , EMAIL_SSL_CERTFILE , EMAIL_SSL_KEYFILE , EMAIL_TIMEOUT , EMAIL_USE_ ... s ... , }, }, } For example, to update these settings: EMAIL_BACKEND = "django.core.mail.backends.smtp.EmailBackend" EMAIL_HOST = "mail.example.net" EMAIL_USE_TLS = True EMAIL_PORT = 587 EMAIL_HOST_USER = "user@example.net" EMAIL_HOST_PASSWORD = "pas ... sword" use: MAILERS = { "default" : { "BACKEND" : "django.core.mail.backends.smtp.EmailBackend" , "OPTIONS" : { "host" : "mail.example.net" , "use_tls" : True , # port is not needed: it defaults to 587 with use_tls True. "username" : "user@ ... 2026年10月08日