Add support for the report-to directive
#357
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
|
Thanks |
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.
This PR extends
DirectiveSetwith thereport-todirective. It is part of CSP Level 3 and intended to replace the deprecatedreport-uridirective.The
report-todirective works with reporting endpoints (from Reporting). The endpoints need to be configured through another header (Reporting-Endpoints, previouslyReport-To). This PR only adds the CSP directive; this enables users to migrate to the new reporting API if they provide the endpoints (via aReporting-Endpointsheader) themselves.I did not deprecate the
report-uridirective because browsers ignore it when areport-todirective is present and the browser supports it. Not all (major) browsers support this directive currently, soreport-uriis still usefull for reporting in all browsers.Fixes #341