Open Bug 1862960 Opened 1 year ago Updated 6 months ago

Implement a proper throttling architecture for CSP reports

Categories

(Core :: DOM: Security, enhancement, P3)

Product:
Core
Component:
DOM: Security
Type:
enhancement

Tracking

()

People

(Reporter: tschuster, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [domsecurity-backlog])

In bug 1839165 I implemented throttling of CSP reports by limiting the amount of reports that are send during a specific time span. We should change that to a proper throttling algorithm that can send the data when the pressure is low.

It also looks like Chrome has some time of delay for sending their reports.

Severity: -- → N/A
Priority: -- → P3
Whiteboard: [domsecurity-backlog]
Duplicate of this bug: 1895056

The "flame graph" showcased as an attachment in bug 1895056 shows how slow we render a page if lots of violations happen. Great test case to optimize for.

You need to log in before you can comment on or make changes to this bug.