... -Security-Policy : Enforces the CSP policy, blocking content that violates the defined directives. Content-Security-Policy-Report-Only : Reports CSP violations without blocking content, allowing for non-intrusive testing. Each policy is composed of one ... dleware is configured using the following settings: SECURE_CSP : defines the enforced Content Security Policy . SECURE_CSP_REPORT_ONLY : defines a report-only Content Security Policy . These settings can be used independently or together Use SECURE_CSP ... alone to enforce a policy that has already been tested and verified. Use SECURE_CSP_REPORT_ONLY on its own to evaluate a new policy without disrupting site behavior. This mode does not block violations, it only lo ... ... -Security-Policy : Enforces the CSP policy, blocking content that violates the defined directives. Content-Security-Policy-Report-Only : Reports CSP violations without blocking content, allowing for non-intrusive testing. Each policy is composed of one ... dleware is configured using the following settings: SECURE_CSP : defines the enforced Content Security Policy . SECURE_CSP_REPORT_ONLY : defines a report-only Content Security Policy . These settings can be used independently or together Use SECURE_CSP ... alone to enforce a policy that has already been tested and verified. Use SECURE_CSP_REPORT_ONLY on its own to evaluate a new policy without disrupting site behavior. This mode does not block violations, it only lo ... ... ntSecurityPolicyMiddleware" , # ... ] Configure the CSP policies in your settings.py using either SECURE_CSP or SECURE_CSP_REPORT_ONLY (or both). The CSP Settings docs provide more details about the differences between these two: from django.utils.csp ... # To enforce a CSP policy: SECURE_CSP = { "default-src" : [ CSP . SELF ], # Add more directives to be enforced. } # Or for report-only mode: SECURE_CSP_REPORT_ONLY = { "default-src" : [ CSP . SELF ], # Add more directives as needed. "report-uri" : "/pa ... th/to/reports-endpoint/" , } Nonce config ¶ To use nonces in your CSP policy, beside the basic config, you need to: Include the NONCE p ... ... team comes to a conclusion. There is no need to chase the security team unless you discover new, relevant information. All reports aim to be resolved within the industry-standard 90 days. Confirmed vulnerabilities with a high severity level will be add ... ng maintainer time ¶ Django's security team are volunteers. Please be mindful and respectful of their time when submitting reports. Your initial report should give the team enough to make a triage decision, no more. It should include: A brief descripti ... er detail at that stage. If you have identified multiple potential issues, please wait for a triage result on your initial report before submitting further ones. Exceptions can be made for issues that are clearly and directly related to an already repo ... ... team comes to a conclusion. There is no need to chase the security team unless you discover new, relevant information. All reports aim to be resolved within the industry-standard 90 days. Confirmed vulnerabilities with a high severity level will be add ... ng maintainer time ¶ Django's security team are volunteers. Please be mindful and respectful of their time when submitting reports. Your initial report should give the team enough to make a triage decision, no more. It should include: A brief descripti ... er detail at that stage. If you have identified multiple potential issues, please wait for a triage result on your initial report before submitting further ones. Exceptions can be made for issues that are clearly and directly related to an already repo ... ... ntSecurityPolicyMiddleware" , # ... ] Configure the CSP policies in your settings.py using either SECURE_CSP or SECURE_CSP_REPORT_ONLY (or both). The CSP Settings docs provide more details about the differences between these two: from django.utils.csp ... # To enforce a CSP policy: SECURE_CSP = { "default-src" : [ CSP . SELF ], # Add more directives to be enforced. } # Or for report-only mode: SECURE_CSP_REPORT_ONLY = { "default-src" : [ CSP . SELF ], # Add more directives as needed. "report-uri" : "/pa ... th/to/reports-endpoint/" , } Nonce config ¶ To use nonces in your CSP policy, beside the basic config, you need to: Include the NONCE p ... ... developers, and its archives are not public. For further details, please see our security policies . バグレポート ¶ Before reporting a bug on the ticket tracker consider these points: Check that someone hasn't already filed the bug report by searching ... 高のバグレポートであり、バグを確認する最善の方法です。 Don't post to Django Forum only to announce that you have filed a bug report. All the tickets are mailed to another list, django-updates , which is tracked by developers and interested community memb ... s they are filed. To understand the lifecycle of your ticket once you have created it, refer to トリアージのワークフロー . Reporting user interface bugs ¶ If your bug impacts anything visual in nature, there are a few additional guidelines to follow: 最 ... ... developers, and its archives are not public. For further details, please see our security policies . バグレポート ¶ Before reporting a bug on the ticket tracker consider these points: Check that someone hasn't already filed the bug report by searching ... 高のバグレポートであり、バグを確認する最善の方法です。 Don't post to Django Forum only to announce that you have filed a bug report. All the tickets are mailed to another list, django-updates , which is tracked by developers and interested community memb ... s they are filed. To understand the lifecycle of your ticket once you have created it, refer to トリアージのワークフロー . Reporting user interface bugs ¶ If your bug impacts anything visual in nature, there are a few additional guidelines to follow: 最 ... ... , combine all coverage statistics by running: / $ coverage combine ...\> coverage combine After that generate the html report by running: / $ coverage html ...\> coverage html When running coverage for the Django tests, the included .coveragerc ... settings file defines coverage_html as the output directory for the report and also excludes several directories not relevant to the results (test code or external code included in Django). Code co ... ntegration (CI) system automatically runs code coverage analysis on pull requests and posts a comment with a diff coverage report. This helps reviewers see which lines in the changed code are covered by tests. What the coverage report shows: The covera ... ... , combine all coverage statistics by running: / $ coverage combine ...\> coverage combine After that generate the html report by running: / $ coverage html ...\> coverage html When running coverage for the Django tests, the included .coveragerc ... settings file defines coverage_html as the output directory for the report and also excludes several directories not relevant to the results (test code or external code included in Django). Code co ... ntegration (CI) system automatically runs code coverage analysis on pull requests and posts a comment with a diff coverage report. This helps reviewers see which lines in the changed code are covered by tests. What the coverage report shows: The covera ... 2026年10月08日