Repository navigation
fix(report): scan pages with a strict CSP or Trusted Types (0.18.3) - #47
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Report mode injects its scan as an inline script plus a style tag. A page with a strict Content-Security-Policy (e.g.
script-src 'self') or Trusted Types (require-trusted-types-for 'script') blocked both, so every route came back as an error with no findings. Two real sites hit this: OpenProject's community site (CSP header) and nx-ng-starter (meta-tag CSP with Trusted Types).The scanning browser context now sets Playwright's
bypassCSP: true, which covers header and<meta>policies and Trusted Types. The app's own policy is unchanged. The CHANGELOG notes that the scan runs without the policy, so problems caused by the policy itself aren't reported.