CSP: Implement report-to
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox130 | --- | fixed |
People
(Reporter: ckerschb, Assigned: freya.laluna, Mentored)
References
(Blocks 2 open bugs, Regressed 1 open bug)
Details
(Keywords: dev-doc-complete, Whiteboard: [domsecurity-backlog1])
Attachments
(2 files)
Reporter | ||
Updated•7 years ago
|
Updated•2 years ago
|
Comment 3•2 years ago
|
||
issue still open since 6+ years blocking consensus for transition report-uri -> report-to.
see: https://w3c.github.io/webappsec-csp/#directive-report-uri
Updated•1 year ago
|
Updated report processing to include support for
report-to directive. Currently supports report-building
and sending through nsCSPContext::SendReports.
Updated•9 months ago
|
Updated•8 months ago
|
Changed how ReportDeliver::Notify is dispatched from ReportDeliver::AppendReportData. Now, instead of relying on a predetermined timer to call Notify, it is dispatched to the current thread queue in a Runnable.
Additionally changed credentials mode to RequestCredentials::Same_origin in ReportDeliver::SendReports to align with W3C reporting specifications,
Updated•6 months ago
|
Updated•6 months ago
|
Is this still being worked on?
Updated•5 months ago
|
Updated•4 months ago
|
Comment 10•3 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/17a0209f5595
https://hg.mozilla.org/mozilla-central/rev/1dd7df601ace
https://hg.mozilla.org/mozilla-central/rev/dcdf8bd23501
Updated•3 months ago
|
Comment 11•2 months ago
•
|
||
FF130 MDN docs work for this can be tracked in https://github.com/mdn/content/issues/35279
EDIT, note, I'm clearing my request for information. After extensive testing I think I know how this works. If I'm wrong we can correct in a post process.
Updated•2 months ago
|
Updated•2 months ago
|
Updated•1 month ago
|
Description
•