per page, with , order by , clip by
Results of 1 - 10 of about 34 for targets (0.002 sec.)
アクセシビリティ — Django 6.1 ドキュメント 13133
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... h as the admin interface and default form rendering, should adhere to established accessibility standards and meet our own targets for supporting specific input devices and assistive technologies. アクセシビリティ基準 ¶ We work to conform with the Web C ... ing will only be needed as a final check. For more complex interfaces, confer with other contributors to decide on testing targets. Reach out to the Accessibility team for support and to coordinate testing. ユーザーインターフェースの変更は、必ず次の方法 ... 上の JAWS Windows 上の Dragon Known issues and how to help ¶ There are parts of Django that do not meet our accessibility targets. We actively work on fixing issues, both as part of ongoing maintenance and bigger overhauls. To learn about known issues, ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
アクセシビリティ — Django 6.1 ドキュメント 12861
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » アクセシビリティ ¶ The Django project is committed to ensuring that websites built with Django are usable by everyone, including people with disabil ... h as the admin interface and default form rendering, should adhere to established accessibility standards and meet our own targets for supporting specific input devices and assistive technologies. アクセシビリティ基準 ¶ We work to conform with the Web C ... ing will only be needed as a final check. For more complex interfaces, confer with other contributors to decide on testing targets. Reach out to the Accessibility team for support and to coordinate testing. ユーザーインターフェースの変更は、必ず次の方法 ... 上の JAWS Windows 上の Dragon Known issues and how to help ¶ There are parts of Django that do not meet our accessibility targets. We actively work on fixing issues, both as part of ongoing maintenance and bigger overhauls. To learn about known issues, ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
Django 1.3.5 リリースノート — Django 6.1 ドキュメント 10097
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl ... relative, or if absolute matches the supplied hostname. This function is intended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third-party sites. 2. All of Django's own built-in vi ... ews -- primarily in the authentication system -- which allow user-supplied redirect targets now use is_safe_url to validate the supplied URL. 目次 Django 1.3.5 リリースノート Host header poisoning Redirect poisonin ...
https://man.mtool.work/django/6.1/releases/1.3.5.html
Django 1.4.3 リリースノート — Django 6.1 ドキュメント 10097
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl ... relative, or if absolute matches the supplied hostname. This function is intended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third-party sites. 2. All of Django's own built-in vi ... ews -- primarily in the authentication system -- which allow user-supplied redirect targets now use is_safe_url to validate the supplied URL. 目次 Django 1.4.3 リリースノート Host header poisoning Redirect poisonin ...
https://man.mtool.work/django/6.1/releases/1.4.3.html
Django 1.3.5 リリースノート — Django 6.1 ドキュメント 9826
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.3.5 リリースノート ¶ December 10, 2012 Django 1.3.5 addresses two security issues present in previous Django releases in the 1.3 series. Pl ... relative, or if absolute matches the supplied hostname. This function is intended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third-party sites. 2. All of Django's own built-in vi ... ews -- primarily in the authentication system -- which allow user-supplied redirect targets now use is_safe_url to validate the supplied URL. 目次 Django 1.3.5 リリースノート Host header poisoning Redirect poisonin ...
https://man.mtool.work/django/6.1/releases/1.3.5.html
Django 1.4.3 リリースノート — Django 6.1 ドキュメント 9826
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.3 リリースノート ¶ December 10, 2012 Django 1.4.3 addresses two security issues present in previous Django releases in the 1.4 series. Pl ... relative, or if absolute matches the supplied hostname. This function is intended for use whenever user-supplied redirect targets are accepted, to ensure that such redirects cannot lead to arbitrary third-party sites. 2. All of Django's own built-in vi ... ews -- primarily in the authentication system -- which allow user-supplied redirect targets now use is_safe_url to validate the supplied URL. 目次 Django 1.4.3 リリースノート Host header poisoning Redirect poisonin ...
https://man.mtool.work/django/6.1/releases/1.4.3.html
Django 1.4.20 リリースノート — Django 6.1 ドキュメント 8164
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.20 リリースノート ¶ March 18, 2015 Django 1.4.20 fixes one security issue in 1.4.19. Mitigated possible XSS attack via user-supplied redi ... ction to an unsafe target isn't a problem either. However, if a developer relies on is_safe_url() to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack as some browsers such as Google Chrome ignore contro ...
https://man.mtool.work/django/6.1/releases/1.4.20.html
Django 1.4.20 リリースノート — Django 6.1 ドキュメント 7876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.20 リリースノート ¶ March 18, 2015 Django 1.4.20 fixes one security issue in 1.4.19. Mitigated possible XSS attack via user-supplied redi ... ction to an unsafe target isn't a problem either. However, if a developer relies on is_safe_url() to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack as some browsers such as Google Chrome ignore contro ...
https://man.mtool.work/django/6.1/releases/1.4.20.html
Django 1.4.6 リリースノート — Django 6.1 ドキュメント 7876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.4.6 リリースノート ¶ August 13, 2013 Django 1.4.6 fixes one security issue present in previous Django releases in the 1.4 series, as well a ... (s) and as such allowed javascript:... URLs to be entered. If a developer relied on is_safe_url() to provide safe redirect targets and put such a URL into a link, they could suffer from a XSS attack. This bug doesn't affect Django currently, since we on ...
https://man.mtool.work/django/6.1/releases/1.4.6.html
Django 1.8.18 リリースノート — Django 6.1 ドキュメント 7876
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.8.18 リリースノート ¶ April 4, 2017 Django 1.8.18 fixes two security issues in 1.8.17. CVE-2017-7233: Open redirect and possible XSS attack ... e.g. http:999999999 ) "safe" when they shouldn't be. Also, if a developer relies on is_safe_url() to provide safe redirect targets and puts such a URL into a link, they could suffer from an XSS attack. CVE-2017-7234: Open redirect vulnerability in djang ...
https://man.mtool.work/django/6.1/releases/1.8.18.html
PREV 1 2 3 4 NEXT