... formance of the Django 1.0 codebase. As such, Django 1.0.2 contains no new features (and, pursuant to our compatibility policy , maintains backwards compatibility with Django 1.0.0), but do ... es contain a number of fixes and other improvements. Django 1.0.2 is a recommended upgrade for any development or deployment currentl ... face of bad Unicode data coming from the __unicode__ method; rather than raise an exception in such cases, repr() will now contain the string "[Bad Unicode data]" in place of the invalid Unicode. A bug involving the interaction of Django's SafeUnicode c ... ... formance of the Django 1.0 codebase. As such, Django 1.0.2 contains no new features (and, pursuant to our compatibility policy , maintains backwards compatibility with Django 1.0.0), but do ... es contain a number of fixes and other improvements. Django 1.0.2 is a recommended upgrade for any development or deployment currentl ... face of bad Unicode data coming from the __unicode__ method; rather than raise an exception in such cases, repr() will now contain the string "[Bad Unicode data]" in place of the invalid Unicode. A bug involving the interaction of Django's SafeUnicode c ... ... formance of the Django 1.1 codebase. Django 1.1.2 maintains backwards compatibility with Django 1.1.0, but contain a number of fixes and other improvements. Django 1.1.2 is a recommended upgrade for any development or deployment currentl ... ut in the case of Django 1.1.2, we have made an exception to this rule. Django 1.2 (the next major release of Django) will contain a feature that will improve protection against Cross-Site Request Forgery (CSRF) attacks. This feature requires the use of ... キーワード code number exit status tests release backwards features branch runner feature csrf token template リリースノート contain incompatibilities failures encoding cookies cookie values characters comma semi クイック検索 Last update: 2026年10月09日 « ... ... formance of the Django 1.1 codebase. Django 1.1.2 maintains backwards compatibility with Django 1.1.0, but contain a number of fixes and other improvements. Django 1.1.2 is a recommended upgrade for any development or deployment currentl ... ut in the case of Django 1.1.2, we have made an exception to this rule. Django 1.2 (the next major release of Django) will contain a feature that will improve protection against Cross-Site Request Forgery (CSRF) attacks. This feature requires the use of ... code number new exit status tests release backwards features branch runner feature csrf token template リリースノート but contain 関連するページ Django 1.2.2 リリースノート Django 1.6 リリースノート Django 1.2.4 リリースノート Unit tests Django 1.2.5 リ ... ... full URLs, including 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 applica ... correct and possibly malicious Host header. For this reason, Django 1.3.6 adds a new setting, ALLOWED_HOSTS , which should contain an explicit list of valid host/domain names for this site. A request with a Host header not matching an entry in this list ... loaddata , but if you feed your own XML documents to the loaddata management command, you will need to ensure they do not contain a DTD. Formset memory exhaustion ¶ Previous versions of Django did not validate or limit the form-count data provided by t ... ... formance of the Django 1.2 codebase. Django 1.2.2 maintains backwards compatibility with Django 1.2.1, but contain a number of fixes and other improvements. Django 1.2.2 is a recommended upgrade for any development or deployment currentl ... スノート backwards feature forms flag second bugfix series improving stability performance codebase maintains compatibility contain number fixes improvements recommended upgrade development クイック検索 Last update: 2026年10月09日 « previous | up | next ... ... full URLs, including 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 applica ... correct and possibly malicious Host header. For this reason, Django 1.3.6 adds a new setting, ALLOWED_HOSTS , which should contain an explicit list of valid host/domain names for this site. A request with a Host header not matching an entry in this list ... loaddata , but if you feed your own XML documents to the loaddata management command, you will need to ensure they do not contain a DTD. Formset memory exhaustion ¶ Previous versions of Django did not validate or limit the form-count data provided by t ... ... ith some forms, most notably the user-editing forms in the Django administrative interface. The packaging manifest did not contain the full list of required files. 前のトピックへ Django 1.2.4 リリースノート 次のトピックへ Django 1.2.2 リリースノート 関連 ... ... ith some forms, most notably the user-editing forms in the Django administrative interface. The packaging manifest did not contain the full list of required files. 前のトピックへ Django 1.2.4 リリースノート 次のトピックへ Django 1.2.2 リリースノート 関連 ... ... equest.COOKIES is simplified to better match the behavior of browsers and to mitigate this attack. request.COOKIES may now contain cookies that are invalid according to RFC 6265 but are possible to set via document.cookie . 目次 Django 1.8.15 リリースノ ... 2026年10月08日