Read a saved content policy and its fallback rules
Admin ·
A catalog page has an enforcing policy and a separate report-only policy for review. Use a saved response to read each policy and its fallback directives.
Read the catalog policy
Choose Load example and Validate CSP. The saved status is 200. The report identifies one enforcing policy and one report-only policy, using their recorded field names.
In the enforcing policy, script-src first names 'self' and then repeats with 'none'. The directives table marks the second entry Repeated because the first occurrence controls that policy.
Read the resource fallback table
In Policy 1, Images falls back to default-src. In Policy 2, Images uses the explicit img-src directive. Frame ancestors has a direct frame-ancestors directive in Policy 1.
Check Form destinations and Base URL separately. These controls have their own directives. The report lists No directive when the selected policy has no declaration for that category.
Keep the disposition with the report
When pasting only a policy value, choose its disposition. If you paste named fields or a saved response, the header names already record whether each policy enforces or reports.
Export JSON to retain the per-policy findings and coverage. Review the results beside the policy text and verify application behavior with the intended browser.
Common questions
Can I analyze multiple enforcing policies?
Yes. The table shows each saved policy separately so you can see its own directives and fallbacks.
Why does the report count source expressions?
The report distinguishes checked source lists from lists that need review without repeating individual nonce, hash, or endpoint values.