#105856CSP reports may flood database
Description
Well formed CSP reports are by default always written to the database and thus may flood it (as I already described/asked here: https://talk.typo3.org/t/solved-possibility-to-deactivate-db-logging-of-csp-reports/6041 ).
You can prevent, and deal with it, but I think it makes sense to have the the logging 1) disabled by default and 2) optionally enabled (e.g. in the site-specific csp.yaml) when configuring CSP. As I was not aware of it, it may thus make more administrators aware of the logging. And prevent offline websites/services due to a full database.
Reviews 4
Related issues 2
History 513
-
Garvin Hicking commented <span data-processor="relativetime" data-value="2024-12-20T11:14:04+00:00" > 12/20/24, 11:14 </span>
-
Oliver Hader changed Related to #105087 <span data-processor="relativetime" data-value="2024-12-24T11:26:34+00:00" > 12/24/24, 11:26 </span>
-
Oliver Hader changed Related to #104570 <span data-processor="relativetime" data-value="2024-12-24T11:27:23+00:00" > 12/24/24, 11:27 </span>
-
Gerrit Code Review changed status
NewUnder Review <span data-processor="relativetime" data-value="2025-01-03T10:09:36+00:00" > 01/03/25, 10:09 </span> -
Gerrit Code Review pushed patch set 1 for main to change 87670 <span data-processor="relativetime" data-value="2025-01-08T14:59:13+00:00" > 01/08/25, 14:59 </span>
-
Gerrit Code Review pushed patch set 2 for main to change 87670 <span data-processor="relativetime" data-value="2025-01-08T18:08:50+00:00" > 01/08/25, 18:08 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 87670 <span data-processor="relativetime" data-value="2025-01-22T15:56:44+00:00" > 01/22/25, 15:56 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 87670 <span data-processor="relativetime" data-value="2025-01-22T19:24:19+00:00" > 01/22/25, 19:24 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 87670 <span data-processor="relativetime" data-value="2025-02-03T13:39:59+00:00" > 02/03/25, 13:39 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 88032 <span data-processor="relativetime" data-value="2025-02-05T12:28:41+00:00" > 02/05/25, 12:28 </span>
-
Gerrit Code Review pushed patch set 1 for 12.4 to change 88033 <span data-processor="relativetime" data-value="2025-02-05T12:55:14+00:00" > 02/05/25, 12:55 </span>
-
Oliver Hader commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-02-05T13:25:14+00:00" > 02/05/25, 13:25 </span>Applied in changeset commit:e4a39fd2087c57363e2e7dee15bca0044e324cb2.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-08-12T14:35:40+00:00" > 08/12/25, 14:35 </span>
In my opinion, it needs to be enabled by default, otherwise CSP would block things you’re not aware off. Doing log rotation/clearing is IMO a task for system maintainers, and watching that for abuse.
(The link offers some solutions how logging can be influenced)