per page, with , order by , clip by
Results of 1 - 10 of about 38 for web browser (0.015 sec.)
web (204), browser (60)
JavaScript code — Django 6.1 ドキュメント 22527
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » JavaScript code ¶ While most of Django core is Python, the admin and gis contrib apps contain JavaScript code. Please follow these coding standards ... ipt performance and minimizing overall admin media file size. JavaScript tests ¶ Django's JavaScript tests can be run in a browser or from the command line. The tests are located in a top level js_tests directory. テストを書く ¶ Django's JavaScript test ... tion for information on the types of assertions supported by QUnit . テストの実行 ¶ The JavaScript tests may be run from a web browser or from the command line. Testing from a web browser ¶ To run the tests from a web browser, open up js_tests/tests ... .html in your browser. To measure code coverage when running the tests, you need to view that file over HTTP. To view code coverage: ルートディレ ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/javascript...
JavaScript code — Django 6.1 ドキュメント 20465
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » JavaScript code ¶ While most of Django core is Python, the admin and gis contrib apps contain JavaScript code. Please follow these coding standards ... ipt performance and minimizing overall admin media file size. JavaScript tests ¶ Django's JavaScript tests can be run in a browser or from the command line. The tests are located in a top level js_tests directory. テストを書く ¶ Django's JavaScript test ... tion for information on the types of assertions supported by QUnit . テストの実行 ¶ The JavaScript tests may be run from a web browser or from the command line. Testing from a web browser ¶ To run the tests from a web browser, open up js_tests/tests ... .html in your browser. To measure code coverage when running the tests, you need to view that file over HTTP. To view code coverage: ルートディレ ...
https://man.mtool.work/django/6.1/internals/contributing/writing-code/javascript...
Django におけるセキュリティ — Django 6.1 ドキュメント 19624
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django におけるセキュリティ ¶ このドキュメントは、Django のセキュリティ機能の概要です。Django を利用したサイトを安全なものにするためのヒントを説明し ... ます。 Real-world security Django's web security implementations have been designed with security for real-world applications in mind. Django is a general-purpose ... web application framework, and its defaults reflect this - they will not be the best solution for every particular case. Speci ... ¶ In a cross-site scripting attack, malicious code in the form of a client-side script is injected into another user's web browser, where it will be executed. This is typically done by: storing the malicious script in the database where it will be retri ...
https://man.mtool.work/django/6.1/topics/security.html
Django におけるセキュリティ — Django 6.1 ドキュメント 19260
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django におけるセキュリティ ¶ このドキュメントは、Django のセキュリティ機能の概要です。Django を利用したサイトを安全なものにするためのヒントを説明し ... ます。 Real-world security Django's web security implementations have been designed with security for real-world applications in mind. Django is a general-purpose ... web application framework, and its defaults reflect this - they will not be the best solution for every particular case. Speci ... ¶ In a cross-site scripting attack, malicious code in the form of a client-side script is injected into another user's web browser, where it will be executed. This is typically done by: storing the malicious script in the database where it will be retri ...
https://man.mtool.work/django/6.1/topics/security.html
アクセシビリティ — Django 6.1 ドキュメント 14054
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 ... rgets for supporting specific input devices and assistive technologies. アクセシビリティ基準 ¶ We work to conform with the Web Content Accessibility Guidelines (WCAG), version 2.2, at the AA level. WCAG is the most established standard for web acces ... f WCAG. Authoring Tool Accessibility Guidelines (ATAG) 2.0 – guidelines for software and services that are used to produce web content. To learn more about accessibility without diving straight into standards, we recommend The A11Y Project , a commu ... put focus. The focus order is inconsistent with the logical order that's communicated visually. The Accessibility Insights browser extension's automated checks feature, or an equivalent tool with the Axe checker. Where the UI changes could affect those ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
コンテンツセキュリティポリシー — Django 6.1 ドキュメント 14044
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » コンテンツセキュリティポリシー ¶ New in Django 6.0. Content Security Policy (CSP) is a web security standard that helps prevent content injection at ... for non-intrusive testing. Each policy is composed of one or more directives and their values, which together instruct the browser on how to handle specific types of content. When the ContentSecurityPolicyMiddleware is enabled, Django automatically buil ... es in behavior, or potential tampering in production environments. Policy violation reports ¶ When a CSP violation occurs, browsers typically log details to the developer console, providing immediate feedback during development. To also receive these re ... scouraged, especially for scripts. WASM_UNSAFE_EVAL ¶ Represents 'wasm-unsafe-eval' . Permits compilation and execution of WebAssembly code without enabling 'unsafe-eval' for scripts. NONCE ¶ Django-specific placeholder value ( "<CSP_NONCE_SENTINEL> ...
https://man.mtool.work/django/6.1/ref/csp.html
アクセシビリティ — Django 6.1 ドキュメント 13969
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 ... rgets for supporting specific input devices and assistive technologies. アクセシビリティ基準 ¶ We work to conform with the Web Content Accessibility Guidelines (WCAG), version 2.2, at the AA level. WCAG is the most established standard for web acces ... f WCAG. Authoring Tool Accessibility Guidelines (ATAG) 2.0 – guidelines for software and services that are used to produce web content. To learn more about accessibility without diving straight into standards, we recommend The A11Y Project , a commu ... put focus. The focus order is inconsistent with the logical order that's communicated visually. The Accessibility Insights browser extension's automated checks feature, or an equivalent tool with the Axe checker. Where the UI changes could affect those ...
https://man.mtool.work/django/6.1/internals/contributing/accessibility.html
コンテンツセキュリティポリシー — Django 6.1 ドキュメント 13927
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » コンテンツセキュリティポリシー ¶ New in Django 6.0. Content Security Policy (CSP) is a web security standard that helps prevent content injection at ... for non-intrusive testing. Each policy is composed of one or more directives and their values, which together instruct the browser on how to handle specific types of content. When the ContentSecurityPolicyMiddleware is enabled, Django automatically buil ... es in behavior, or potential tampering in production environments. Policy violation reports ¶ When a CSP violation occurs, browsers typically log details to the developer console, providing immediate feedback during development. To also receive these re ... scouraged, especially for scripts. WASM_UNSAFE_EVAL ¶ Represents 'wasm-unsafe-eval' . Permits compilation and execution of WebAssembly code without enabling 'unsafe-eval' for scripts. NONCE ¶ Django-specific placeholder value ( "<CSP_NONCE_SENTINEL> ...
https://man.mtool.work/django/6.1/ref/csp.html
Django 1.1.4 リリースノート — Django 6.1 ドキュメント 13210
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1.4 リリースノート ¶ Django 1.1.4 へようこそ! This is the fourth "bugfix" release in the Django 1.1 series, improving the stability and per ... on for AJAX requests, on the following basis: Many AJAX toolkits add an X-Requested-With header when using XMLHttpRequest. Browsers have strict same-origin policies regarding XMLHttpRequest. In the context of a browser, the only way that a custom header ... not apply CSRF checks to requests that appeared to be AJAX on the basis of the X-Requested-With header. The Ruby on Rails web framework had a similar exemption. Recently, engineers at Google made members of the Ruby on Rails development team aware ... of a combination of browser plugins and redirects which can allow an attacker to provide custom HTTP headers on a request to any website. This can all ...
https://man.mtool.work/django/6.1/releases/1.1.4.html
Django 1.1.4 リリースノート — Django 6.1 ドキュメント 13210
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django 1.1.4 リリースノート ¶ Django 1.1.4 へようこそ! This is the fourth "bugfix" release in the Django 1.1 series, improving the stability and per ... on for AJAX requests, on the following basis: Many AJAX toolkits add an X-Requested-With header when using XMLHttpRequest. Browsers have strict same-origin policies regarding XMLHttpRequest. In the context of a browser, the only way that a custom header ... not apply CSRF checks to requests that appeared to be AJAX on the basis of the X-Requested-With header. The Ruby on Rails web framework had a similar exemption. Recently, engineers at Google made members of the Ruby on Rails development team aware ... of a combination of browser plugins and redirects which can allow an attacker to provide custom HTTP headers on a request to any website. This can all ...
https://man.mtool.work/django/6.1/releases/1.1.4.html
PREV 1 2 3 4 NEXT