-
Notifications
You must be signed in to change notification settings - Fork 179
Description
I'm attempting to use Permissions-Policy reporting in Chrome (Canary, v143). It works, and reports are triggered, but they are always sent to "Default", which I have not defined. I'm finding the descriptions of how to set the report-to directive very cryptic – an example would go a very long way to clarifying this.
Member Values may have a Parameter named "report-to", whose value must be a String. Any other parameters will be ignored.
For each feature-name → (value, params) of dictionary:
If feature-name does not identify any recognized policy-controlled feature, then continue.
Let feature be the policy-controlled feature identified by feature-name.
If params["report-to"] exists, and is a string, then set reporting-config[feature] to params["report-to"].
I have a named endpoint called csp set via both Report-To and Reporting-Endpoints headers, and I've tried all these combinations, without success; the reports are always sent to "Default":
Permissions-Policy: geolocation=(); report-to=csp
Permissions-Policy: geolocation=(), report-to=csp
Permissions-Policy: geolocation=(); report-to="csp"
Permissions-Policy: geolocation=(), report-to="csp"
Permissions-Policy: geolocation=(report-to=csp)
Permissions-Policy: geolocation=(report-to="csp")
Permissions-Policy: geolocation=(,report-to=csp)
Permissions-Policy: geolocation=(,report-to="csp")
Permissions-Policy: geolocation=(;report-to=csp)
Permissions-Policy: geolocation=(;report-to="csp")
As it stands, I can't tell whether this is due to an incomplete/buggy implementation in Chrome, or because I've not stumbled across the correct format, but either way, I'm not finding that the spec makes it clear.