per page, with , order by , clip by
Results of 1 - 10 of about 60 for browser (0.005 sec.)
JavaScript code — Django 6.1 ドキュメント 13916
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 ... 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 ドキュメント 12709
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 ... 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 ドキュメント 9816
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django におけるセキュリティ ¶ このドキュメントは、Django のセキュリティ機能の概要です。Django を利用したサイトを安全なものにするためのヒントを説明し ... ¶ 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 ... eved and presented to other users in their browsers, or getting users to click a link which will cause the attacker's JavaScript to be executed by the user's browser. Cross- ... acks by automatically escaping characters that represent a risk (that is, HTML characters that could be interpreted by the browser to malicious effect are instead safely displayed ). However, the extent of this protection and its limitations should be u ...
https://man.mtool.work/django/6.1/topics/security.html
Django におけるセキュリティ — Django 6.1 ドキュメント 9452
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » Django におけるセキュリティ ¶ このドキュメントは、Django のセキュリティ機能の概要です。Django を利用したサイトを安全なものにするためのヒントを説明し ... ¶ 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 ... eved and presented to other users in their browsers, or getting users to click a link which will cause the attacker's JavaScript to be executed by the user's browser. Cross- ... acks by automatically escaping characters that represent a risk (that is, HTML characters that could be interpreted by the browser to malicious effect are instead safely displayed ). However, the extent of this protection and its limitations should be u ...
https://man.mtool.work/django/6.1/topics/security.html
コンテンツセキュリティポリシー — Django 6.1 ドキュメント 9205
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 ... ango supports configuring these directives via the SECURE_CSP_REPORT_ONLY settings, but reports will only be issued by the browser if the policy explicitly includes a valid reporting directive. Django does not provide built-in functionality to receive, ...
https://man.mtool.work/django/6.1/ref/csp.html
コンテンツセキュリティポリシー — Django 6.1 ドキュメント 9088
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 ... ango supports configuring these directives via the SECURE_CSP_REPORT_ONLY settings, but reports will only be issued by the browser if the policy explicitly includes a valid reporting directive. Django does not provide built-in functionality to receive, ...
https://man.mtool.work/django/6.1/ref/csp.html
セッションの使いかた — Django 6.1 ドキュメント 8725
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » セッションの使いかた ¶ Django は、匿名のセッションをフルサポートしています。このセッションフレームワークを使えば、任意のデータを、サイトの訪問者ごと ... session cookie. This is used if you want to ensure that the previous session data can't be accessed again from the user's browser (for example, the django.contrib.auth.logout() function calls it). is_empty () ¶ Returns True if the session does not have ... 等しいです。 この関数は、 get_expiry_age() と同じキーワード引数を取ることができ、使用の際の注意点も同じです。 get_expire_at_browser_close () ¶ aget_expire_at_browser_close () ¶ 非同期バージョン : aget_expire_at_browser_close() ユーザのセッションクッキーが ... が 500 の時には、セッションは保存されません。 ブラウザ起動中のみ有効なセッション vs. 永続的なセッション ¶ SESSION_EXPIRE_AT_BROWSER_CLOSE 設定を使うと、セッションフレームワークが、ブラウザ起動中のみ有効なセッションと永続的なセッションのどちらを使うか設定 ...
https://man.mtool.work/django/6.1/topics/http/sessions.html
セッションの使いかた — Django 6.1 ドキュメント 8725
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » セッションの使いかた ¶ Django は、匿名のセッションをフルサポートしています。このセッションフレームワークを使えば、任意のデータを、サイトの訪問者ごと ... session cookie. This is used if you want to ensure that the previous session data can't be accessed again from the user's browser (for example, the django.contrib.auth.logout() function calls it). is_empty () ¶ Returns True if the session does not have ... 等しいです。 この関数は、 get_expiry_age() と同じキーワード引数を取ることができ、使用の際の注意点も同じです。 get_expire_at_browser_close () ¶ aget_expire_at_browser_close () ¶ 非同期バージョン : aget_expire_at_browser_close() ユーザのセッションクッキーが ... が 500 の時には、セッションは保存されません。 ブラウザ起動中のみ有効なセッション vs. 永続的なセッション ¶ SESSION_EXPIRE_AT_BROWSER_CLOSE 設定を使うと、セッションフレームワークが、ブラウザ起動中のみ有効なセッションと永続的なセッションのどちらを使うか設定 ...
https://man.mtool.work/django/6.1/topics/http/sessions.html
ドキュメントを書く — Django 6.1 ドキュメント 8361
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » ドキュメントを書く ¶ 私たちはドキュメントの一貫性と読みやすさを重要視しています。結局のところ、Django はジャーナリズムの環境で作られました!ですから、 ... ebuilds ¶ sphinx-autobuild can be used to automatically rebuild the documentation and reload the documentation page in the browser whenever a file changes. To enable auto-reloading: Install the package: /  $ python -m pip install sphinx-autobuild ... ... cs directory, run one of the following commands: On Linux and macOS: $ SPHINXBUILD = sphinx-autobuild SPHINXOPTS = "--open-browser --delay 0" make html On Windows (Command Prompt): ...\> set SPHINXBUILD = sphinx-autobuild ...\> set SPHINXOPTS = --open-b ... delay 0 ...\> make html On Windows (PowerShell): PS > $env:SPHINXBUILD = "sphinx-autobuild" PS > $env:SPHINXOPTS = "--open-browser --delay 0" PS > make html Alternatively, sphinx-autobuild can be invoked directly: /  $ sphinx-autobuild . _build/html ...
https://man.mtool.work/django/6.1/internals/contributing/writing-documentation.h...
ドキュメントを書く — Django 6.1 ドキュメント 8361
Django 6.1 ドキュメント Home | Table of contents | Index | Modules « previous | up | next » ドキュメントを書く ¶ 私たちはドキュメントの一貫性と読みやすさを重要視しています。結局のところ、Django はジャーナリズムの環境で作られました!ですから、 ... ebuilds ¶ sphinx-autobuild can be used to automatically rebuild the documentation and reload the documentation page in the browser whenever a file changes. To enable auto-reloading: Install the package: /  $ python -m pip install sphinx-autobuild ... ... cs directory, run one of the following commands: On Linux and macOS: $ SPHINXBUILD = sphinx-autobuild SPHINXOPTS = "--open-browser --delay 0" make html On Windows (Command Prompt): ...\> set SPHINXBUILD = sphinx-autobuild ...\> set SPHINXOPTS = --open-b ... delay 0 ...\> make html On Windows (PowerShell): PS > $env:SPHINXBUILD = "sphinx-autobuild" PS > $env:SPHINXOPTS = "--open-browser --delay 0" PS > make html Alternatively, sphinx-autobuild can be invoked directly: /  $ sphinx-autobuild . _build/html ...
https://man.mtool.work/django/6.1/internals/contributing/writing-documentation.h...
PREV 1 2 3 4 5 6 NEXT