CSP report-to enabled in Chrome 70 #3550
Merged
Conversation
This file contains 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
gapple
force-pushed
the
csp-report-to
branch
from
a6f91a2
to
93f5376
Compare
jpmedley
requested changes
Feb 28, 2019
Elchi3
added
the
data:http 🚠
gapple
force-pushed
the
csp-report-to
branch
from
93f5376
to
8231772
Compare
Elchi3
approved these changes
Feb 28, 2019
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.
In September 2018, the Content Security Policy
report-todirective was put behind the Reporting API feature flag (https://bugs.chromium.org/p/chromium/issues/detail?id=726634#c18), and theReport-Toheader was then enabled in Chrome 70 for Intervention and Deprecation reports (https://developers.google.com/web/updates/2018/10/nic70#more, https://www.chromestatus.com/feature/5544632075157504), which also enabled it for CSP.I tested sending/receiving CSP reports via
report-toin Chrome 71.