feat: Enable CSP with Nonce in the Report Only Header #840
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.
I observed a number of customers that only use the
content-security-policy-report-only
header.This header enables the CSP in a nonblocking fashion, simply reporting potential violations to a specified endpoint.
It could make it more comfortable for customers to try out the nonce + strict-dynamic based CSP if they could do it in production, without affecting the website for start.
Note: according to https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Content-Security-Policy-Report-Only , this header is not supported as a meta tag.