Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add back report_uri CSP directive until Reporting API stabilises #16

Closed
oplik0 opened this issue Jun 11, 2021 · 1 comment · Fixed by #18
Closed

Add back report_uri CSP directive until Reporting API stabilises #16

oplik0 opened this issue Jun 11, 2021 · 1 comment · Fixed by #18

Comments

@oplik0
Copy link
Contributor

oplik0 commented Jun 11, 2021

While the report_uri directive is deprecated, currently Report-To header required for report-to directive was removed from spec before it even became a Candidate Recommendation. Instead, current ED of Reporting API has a Reporting-Endpoints header that doesn't use the JSON values like the previous one, instead opting for a simpler groupname="url" syntax (with ability to add multiple comma-separated entries).
Considering that according to caniuse only about 70% of users have support for Report-To header, while over 93% support report-uri directive, for now report-uri seems to be more widely supported and could even live longer than Report-To header.

It can be added as a custom directive, but I think it'd be a good idea to re-add it as a normal directive. report-to CSP directive is still the way to go in the future, but for now it's much less practical due to its companion header not being truly widely supported yet and on its way to be replaced soon.

@cak
Copy link
Member

cak commented Jul 16, 2021

Thanks for the suggestion, I'll get this added!

oplik0 added a commit to oplik0/secure that referenced this issue Jul 23, 2021
@cak cak closed this as completed in #18 Aug 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants