per page, with , order by , clip by
Results of 1 - 10 of about 92 for correctly (0.002 sec.)
Django 1.4.13 リリースノート — Django 6.1 ドキュメント 11488
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.13 リリースノート ¶ May 14, 2014 Django 1.4.13 fixes two security issues in 1.4.12. Caches may incorrectly be allowed to store and serve ... ition header have also been removed as they were found to have similar issues. Malformed redirect URLs from user input not correctly validated ¶ The validation for redirects did not correctly validate some malformed URLs, which are accepted by some browse ... the user to an "on success" URL. The security checks for these redirects (namely django.utils.http.is_safe_url() ) did not correctly validate some malformed URLs, such as http:\\\\\\djangoproject.com , which are accepted by some browsers with more liberal ... URL parsing. To remedy this, the validation in is_safe_url() has been tightened to be able to handle and correctly validate these malformed URLs. 目次 Django 1.4.13 リリースノート Caches may incorrectly be allowed to store and serve priv ...
https://man.mtool.work/django/6.1/releases/1.4.13.html
Django 1.5.8 リリースノート — Django 6.1 ドキュメント 11488
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5.8 リリースノート ¶ May 14, 2014 Django 1.5.8 fixes two security issues in 1.5.8. Caches may incorrectly be allowed to store and serve pri ... ition header have also been removed as they were found to have similar issues. Malformed redirect URLs from user input not correctly validated ¶ The validation for redirects did not correctly validate some malformed URLs, which are accepted by some browse ... the user to an "on success" URL. The security checks for these redirects (namely django.utils.http.is_safe_url() ) did not correctly validate some malformed URLs, such as http:\\\\\\djangoproject.com , which are accepted by some browsers with more liberal ... URL parsing. To remedy this, the validation in is_safe_url() has been tightened to be able to handle and correctly validate these malformed URLs. 目次 Django 1.5.8 リリースノート Caches may incorrectly be allowed to store and serve priva ...
https://man.mtool.work/django/6.1/releases/1.5.8.html
Django 1.4.13 リリースノート — Django 6.1 ドキュメント 11183
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.13 リリースノート ¶ May 14, 2014 Django 1.4.13 fixes two security issues in 1.4.12. Caches may incorrectly be allowed to store and serve ... ition header have also been removed as they were found to have similar issues. Malformed redirect URLs from user input not correctly validated ¶ The validation for redirects did not correctly validate some malformed URLs, which are accepted by some browse ... the user to an "on success" URL. The security checks for these redirects (namely django.utils.http.is_safe_url() ) did not correctly validate some malformed URLs, such as http:\\\\\\djangoproject.com , which are accepted by some browsers with more liberal ... URL parsing. To remedy this, the validation in is_safe_url() has been tightened to be able to handle and correctly validate these malformed URLs. 目次 Django 1.4.13 リリースノート Caches may incorrectly be allowed to store and serve priv ...
https://man.mtool.work/django/6.1/releases/1.4.13.html
Django 1.5.8 リリースノート — Django 6.1 ドキュメント 11183
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.5.8 リリースノート ¶ May 14, 2014 Django 1.5.8 fixes two security issues in 1.5.8. Caches may incorrectly be allowed to store and serve pri ... ition header have also been removed as they were found to have similar issues. Malformed redirect URLs from user input not correctly validated ¶ The validation for redirects did not correctly validate some malformed URLs, which are accepted by some browse ... the user to an "on success" URL. The security checks for these redirects (namely django.utils.http.is_safe_url() ) did not correctly validate some malformed URLs, such as http:\\\\\\djangoproject.com , which are accepted by some browsers with more liberal ... URL parsing. To remedy this, the validation in is_safe_url() has been tightened to be able to handle and correctly validate these malformed URLs. 目次 Django 1.5.8 リリースノート Caches may incorrectly be allowed to store and serve priva ...
https://man.mtool.work/django/6.1/releases/1.5.8.html
Django 1.6.5 リリースノート — Django 6.1 ドキュメント 11077
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6.5 リリースノート ¶ May 14, 2014 Django 1.6.5 fixes two security issues and several bugs in 1.6.4. Issue: Caches may incorrectly be allowe ... eader have also been removed as they were found to have similar issues. Issue: Malformed redirect URLs from user input not correctly validated ¶ The validation for redirects did not correctly validate some malformed URLs, which are accepted by some browse ... the user to an "on success" URL. The security checks for these redirects (namely django.utils.http.is_safe_url() ) did not correctly validate some malformed URLs, such as http:\\\\\\djangoproject.com , which are accepted by some browsers with more liberal ... URL parsing. To remedy this, the validation in is_safe_url() has been tightened to be able to handle and correctly validate these malformed URLs. バグ修正 ¶ Made the year_lookup_bounds_for_datetime_field Oracle backend method Python 3 co ...
https://man.mtool.work/django/6.1/releases/1.6.5.html
Django 1.6.5 リリースノート — Django 6.1 ドキュメント 10878
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.6.5 リリースノート ¶ May 14, 2014 Django 1.6.5 fixes two security issues and several bugs in 1.6.4. Issue: Caches may incorrectly be allowe ... eader have also been removed as they were found to have similar issues. Issue: Malformed redirect URLs from user input not correctly validated ¶ The validation for redirects did not correctly validate some malformed URLs, which are accepted by some browse ... the user to an "on success" URL. The security checks for these redirects (namely django.utils.http.is_safe_url() ) did not correctly validate some malformed URLs, such as http:\\\\\\djangoproject.com , which are accepted by some browsers with more liberal ... URL parsing. To remedy this, the validation in is_safe_url() has been tightened to be able to handle and correctly validate these malformed URLs. バグ修正 ¶ Made the year_lookup_bounds_for_datetime_field Oracle backend method Python 3 co ...
https://man.mtool.work/django/6.1/releases/1.6.5.html
Django 1.7.6 リリースノート — Django 6.1 ドキュメント 9153
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7.6 リリースノート ¶ March 9, 2015 Django 1.7.6 fixes a security issue and several bugs in 1.7.5. Mitigated an XSS attack via properties in ... n.readonly_fields attribute in the Django admin allows displaying model fields and model attributes. While the former were correctly escaped, the latter were not. Thus untrusted content could be injected into the admin, presenting an exploitation vector f ... g. a property ) will fail to be escaped even if that attribute is not marked as safe. In this release, autoescaping is now correctly applied. バグ修正 ¶ Fixed crash when coercing ManyRelatedManager to a string ( #24352 ). Fixed a bug that prevented migrat ... リースノート 次のトピックへ Django 1.7.5 リリースノート 関連キーワード fields model readonly attribute ModelAdmin admin were correctly escaped Fixed foreign リリースノート March fixes security issue several bugs Mitigated attack properties allows displaying ...
https://man.mtool.work/django/6.1/releases/1.7.6.html
Django 1.7.6 リリースノート — Django 6.1 ドキュメント 8848
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.7.6 リリースノート ¶ March 9, 2015 Django 1.7.6 fixes a security issue and several bugs in 1.7.5. Mitigated an XSS attack via properties in ... n.readonly_fields attribute in the Django admin allows displaying model fields and model attributes. While the former were correctly escaped, the latter were not. Thus untrusted content could be injected into the admin, presenting an exploitation vector f ... g. a property ) will fail to be escaped even if that attribute is not marked as safe. In this release, autoescaping is now correctly applied. バグ修正 ¶ Fixed crash when coercing ManyRelatedManager to a string ( #24352 ). Fixed a bug that prevented migrat ... ート 次のトピックへ Django 1.7.5 リリースノート 関連キーワード fields model Django readonly attribute ModelAdmin admin were correctly escaped field Fixed foreign key リリースノート March fixes security issue several 関連するページ Django 1.10.6 リリースノー ...
https://man.mtool.work/django/6.1/releases/1.7.6.html
Django 3.1.2 リリースノート — Django 6.1 ドキュメント 7840
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 3.1.2 リリースノート ¶ October 1, 2020 Django 3.1.2 では、3.1.1 におけるいくつかのバグを修正しました。 バグ修正 ¶ Fixed a bug in Django 3.1 w ... here FileField instances with a callable storage were not correctly deconstructed ( #31941 ). Fixed a regression in Django 3.1 where the QuerySet.ordered attribute returned incorrectly True ... バグ 修正 queries Meta ordering crash database using admin リリースノート October FileField instances callable storage were correctly deconstructed QuerySet ordered attribute returned incorrectly クイック検索 Last update: 2026年10月09日 « previous | up | n ...
https://man.mtool.work/django/6.1/releases/3.1.2.html
コードのコミット — Django 6.1 ドキュメント 6726
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » コードのコミット ¶ This section is addressed to the mergers and to anyone interested in knowing how code gets committed into Django. The コミットガイ ... e, you can omit "--ff-only" since you just rebased) $ git merge --ff-only pr/XXXX $ # If you're not sure if you did things correctly, check that only the $ # changes you expect will be pushed to upstream. $ git push --dry-run upstream main $ # Push! $ git ... omit "--ff-only" since you just rebased) ...\> git merge --ff-only pr/XXXX ...\> REM If you're not sure if you did things correctly, check that only the ...\> REM changes you expect will be pushed to upstream. ...\> git push --dry-run upstream main ...\> ... ry-pick --continue before amending. This option requires no setup but relies entirely on remembering to format the message correctly. Option 2: using the helper script in the repo The scripts/backport.sh Bash script automates the cherry-pick and rewrites ...
https://man.mtool.work/django/6.1/internals/contributing/committing-code.html
PREV 1 2 3 4 5 6 7 8 9 10 NEXT