#102079CSP violation Event
Description
We would very much like to have an additional Event dispatch when an CSP violation happens.
In the case where some external javascript changes or someone adds some external javascript it would be nice
to be able to enable some kind of notification. For example by email or Slack or something else…
Our worry is that without any notification the violation could be unhandled for longer periods of time which could
leads to other and larger problems (loss of revenues, customer experience etc).
Our suggestion/idea is to dispatch an event right after the report is persisted. To keep it simple the whole report is dispatched, thus
making it the eventlisteners job to handle what/when/how notification are sent based on the incoming report.
Example gists:
https://gist.github.com/hdj-typoconsult/71a06fd4af042aed7d3efa4f3ba2c67b
https://gist.github.com/hdj-typoconsult/fbf3579a2ba38a347c1f488976116852
Reviews 1
Related issues 2
History 917
-
Claus Harup changed category <span data-processor="relativetime" data-value="2023-10-02T11:10:19+00:00" > 10/02/23, 11:10 </span>
-
Oliver Hader changed Tags csp <span data-processor="relativetime" data-value="2023-10-18T14:37:02+00:00" > 10/18/23, 14:37 </span>
-
Henrik Jensen commented <span data-processor="relativetime" data-value="2023-10-23T06:46:00+00:00" > 10/23/23, 06:46 </span>
Oliver Hader wrote in #note-3:
> Sounds good… maybe there’s also a demand for pre-filtering these reports – e.g. having an event that allows to skip persisting particular reports (e.g. those coming from browser extensions).That is a good idea too.
-
Georg Ringer changed category <span data-processor="relativetime" data-value="2024-06-11T16:34:16+00:00" > 06/11/24, 16:34 </span>
-
Oliver Hader changed Related to #101797 <span data-processor="relativetime" data-value="2024-08-14T11:51:54+00:00" > 08/14/24, 11:51 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 90515 status
NewUnder Review <span data-processor="relativetime" data-value="2025-08-29T16:44:43+00:00" > 08/29/25, 16:44 </span> -
Gerrit Code Review pushed patch set 2 for main to change 90515 <span data-processor="relativetime" data-value="2025-08-29T16:49:31+00:00" > 08/29/25, 16:49 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 90515 <span data-processor="relativetime" data-value="2025-08-29T17:29:33+00:00" > 08/29/25, 17:29 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 90515 <span data-processor="relativetime" data-value="2025-08-30T08:23:16+00:00" > 08/30/25, 08:23 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 90515 <span data-processor="relativetime" data-value="2026-02-07T09:09:29+00:00" > 02/07/26, 09:09 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 90515 <span data-processor="relativetime" data-value="2026-02-18T21:30:41+00:00" > 02/18/26, 21:30 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 90515 <span data-processor="relativetime" data-value="2026-02-19T09:40:19+00:00" > 02/19/26, 09:40 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 90515 <span data-processor="relativetime" data-value="2026-02-19T10:06:08+00:00" > 02/19/26, 10:06 </span>
-
Oliver Hader commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2026-02-19T13:40:08+00:00" > 02/19/26, 13:40 </span>Applied in changeset commit:7b69b42337086c547c082e1e5bbb11415f3e39c9.
-
Oliver Hader changed Related to #109416 <span data-processor="relativetime" data-value="2026-03-28T16:05:03+00:00" > 03/28/26, 16:05 </span>
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2026-03-31T09:00:36+00:00" > 03/31/26, 09:00 </span>
Sounds good… maybe there’s also a demand for pre-filtering these reports – e.g. having an event that allows to skip persisting particular reports (e.g. those coming from browser extensions).