Open
Bug 1391243
Opened 7 years ago
Updated 14 days ago
CSP: Implement report-to
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Core
DOM: Core & HTML
Tracking
()
ASSIGNED
People
(Reporter: ckerschb, Assigned: freya.laluna, Mentored)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [domsecurity-backlog1])
Attachments
(2 files)
Reporter | ||
Updated•7 years ago
|
Updated•2 years ago
|
Severity: normal → S3
Comment 3•1 year 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•7 months ago
|
Component: DOM: Security → DOM: Core & HTML
Updated report processing to include support for
report-to directive. Currently supports report-building
and sending through nsCSPContext::SendReports.
Updated•4 months ago
|
Mentor: sefeng
Updated•3 months ago
|
Assignee: nobody → freya.laluna
Status: NEW → ASSIGNED
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•16 days ago
|
Attachment #9370668 -
Attachment description: WIP: Bug 1391243 - Implementing Report-To Directive → Bug 1391243 - Implementing Report-To Directive
Updated•14 days ago
|
Attachment #9387944 -
Attachment description: WIP: Bug 1391243 - Revised ReportDeliver Notify Method → Bug 1391243 - Revised ReportDeliver Notify Method
You need to log in
before you can comment on or make changes to this bug.
Description
•