#107062CSP handling disables Caching
Description
As soon as any kind of Content Security Policy handling is configured, TSFE adds the http header ‘Cache-Control: private, no-store’ (line 2426, as of v. 12.4.33) to the rendered page. https://docs.typo3.org/m/typo3/reference-coreapi/main/en-us/ApiOverview/ContentSecurityPolicy/Index.html#notes-about-nonces-and-caching mentions this behaviour. This leads (at least in one of my projects) to a situation where no pages are cached within our CDN.
From my point of view, the basic problem is that \TYPO3\CMS\Frontend\Middleware\ContentSecurityPolicyHeaders.php adds the attribute ‘nonce’ to the request, even if there is no CSP mutation requiring nonces. I would like to propose a change in that class, so that the ‘nonce’ attribute is only added to the request, if any of the CSP mutations make use of such features.
I’ve written a (sketchy) patch that solves the problem within my project (see the attached file) and would like to suggest an equivalent change in the core.
Thanks & cheers
Sven
Reviews 3
Related issues 2
Files 1
History 742
Show 417 earlier messages
-
Oliver Hader changed Related to #100887 <span data-processor="relativetime" data-value="2025-07-09T12:15:03+00:00" > 07/09/25, 12:15 </span>
-
Oliver Hader commented <span data-processor="relativetime" data-value="2025-07-09T12:30:24+00:00" > 07/09/25, 12:30 </span>
I guess it’s possible to extract “nonce dropping” from https://review.typo3.org/c/Packages/TYPO3.CMS/+/80554 into a separate patch.
-
Oliver Hader changed status
NewAccepted <span data-processor="relativetime" data-value="2025-07-09T12:30:54+00:00" > 07/09/25, 12:30 </span> -
Gerrit Code Review pushed patch set 1 for main to change 90814 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2025-09-26T15:44:57+00:00" > 09/26/25, 15:44 </span> -
Gerrit Code Review pushed patch set 2 for main to change 90814 <span data-processor="relativetime" data-value="2025-09-26T15:56:54+00:00" > 09/26/25, 15:56 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 90814 <span data-processor="relativetime" data-value="2025-09-28T18:34:40+00:00" > 09/28/25, 18:34 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 90814 <span data-processor="relativetime" data-value="2025-09-29T07:45:52+00:00" > 09/29/25, 07:45 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-06T16:43:33+00:00" > 10/06/25, 16:43 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-07T19:16:50+00:00" > 10/07/25, 19:16 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-07T19:41:56+00:00" > 10/07/25, 19:41 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-07T20:00:32+00:00" > 10/07/25, 20:00 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-07T20:49:12+00:00" > 10/07/25, 20:49 </span>
-
Gerrit Code Review pushed patch set 10 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-07T21:17:30+00:00" > 10/07/25, 21:17 </span>
-
Gerrit Code Review pushed patch set 11 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-07T22:04:19+00:00" > 10/07/25, 22:04 </span>
-
Gerrit Code Review pushed patch set 12 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-08T08:55:50+00:00" > 10/08/25, 08:55 </span>
-
Gerrit Code Review pushed patch set 13 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-08T13:53:24+00:00" > 10/08/25, 13:53 </span>
-
Gerrit Code Review pushed patch set 14 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-08T23:19:17+00:00" > 10/08/25, 23:19 </span>
-
Gerrit Code Review pushed patch set 15 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-09T18:28:34+00:00" > 10/09/25, 18:28 </span>
-
Gerrit Code Review pushed patch set 16 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-13T07:33:15+00:00" > 10/13/25, 07:33 </span>
-
Gerrit Code Review pushed patch set 17 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-14T11:56:26+00:00" > 10/14/25, 11:56 </span>
-
Gerrit Code Review pushed patch set 1 for 13.4 to change 91063 <span data-processor="relativetime" data-value="2025-10-14T11:59:09+00:00" > 10/14/25, 11:59 </span>
-
Gerrit Code Review pushed patch set 18 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-14T20:52:10+00:00" > 10/14/25, 20:52 </span>
-
Gerrit Code Review pushed patch set 19 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-15T09:41:43+00:00" > 10/15/25, 09:41 </span>
-
Gerrit Code Review pushed patch set 20 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-19T17:15:50+00:00" > 10/19/25, 17:15 </span>
-
Gerrit Code Review pushed patch set 2 for 13.4 to change 91063 <span data-processor="relativetime" data-value="2025-10-20T10:07:43+00:00" > 10/20/25, 10:07 </span>
-
Gerrit Code Review pushed patch set 21 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-23T11:25:22+00:00" > 10/23/25, 11:25 </span>
-
Gerrit Code Review pushed patch set 22 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-27T16:06:30+00:00" > 10/27/25, 16:06 </span>
-
Gerrit Code Review pushed patch set 23 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-27T16:32:12+00:00" > 10/27/25, 16:32 </span>
-
Gerrit Code Review pushed patch set 24 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-27T16:40:50+00:00" > 10/27/25, 16:40 </span>
-
Gerrit Code Review pushed patch set 3 for 13.4 to change 91063 <span data-processor="relativetime" data-value="2025-10-27T16:43:18+00:00" > 10/27/25, 16:43 </span>
-
Gerrit Code Review pushed patch set 25 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-28T13:20:36+00:00" > 10/28/25, 13:20 </span>
-
Gerrit Code Review pushed patch set 26 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-28T13:41:50+00:00" > 10/28/25, 13:41 </span>
-
Gerrit Code Review pushed patch set 27 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-28T19:49:45+00:00" > 10/28/25, 19:49 </span>
-
Gerrit Code Review pushed patch set 28 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-28T19:52:23+00:00" > 10/28/25, 19:52 </span>
-
Gerrit Code Review pushed patch set 29 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-28T19:53:44+00:00" > 10/28/25, 19:53 </span>
-
Gerrit Code Review pushed patch set 4 for 13.4 to change 91063 <span data-processor="relativetime" data-value="2025-10-28T21:00:04+00:00" > 10/28/25, 21:00 </span>
-
Gerrit Code Review pushed patch set 30 for main to change 90814 <span data-processor="relativetime" data-value="2025-10-30T13:12:17+00:00" > 10/30/25, 13:12 </span>
-
Gerrit Code Review pushed patch set 5 for 13.4 to change 91063 <span data-processor="relativetime" data-value="2025-10-30T16:00:20+00:00" > 10/30/25, 16:00 </span>
-
Oliver Hader commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-10-30T16:25:08+00:00" > 10/30/25, 16:25 </span>Applied in changeset commit:80f74700c14c4f40a083127a39c2e536a83a6de8.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T13:57:57+00:00" > 12/02/25, 13:57 </span> -
Georg Ringer changed Related to #108422 <span data-processor="relativetime" data-value="2025-12-11T18:46:46+00:00" > 12/11/25, 18:46 </span>
Thanks for providing the patch. Unfortunately the scenario is a bit more complicated.
The request object is used to populate the nonce value to all potential consumers and should not be omitted (otherwise components the need to assign a nonce value, cannot continue).
The decision, whether to put nonce to the CSP header would happen in the
PolicyProvider(since nonce values could have been requested dynamically, in site configs, in extension configs or via mutations persisted in the database).The patch for issue #100887 (pending since August 2023) does it like this:
The decision whether to omit nonce values shall be explicit, by introducing a new
behaviorsection forcsp.yamlin the frontend:behavior: useNonce: drop useHash: allow enforceUnsafeInlineFor: - style-src - style-src-attr - style-str-elemIn the YAML example above basically only
useNonce: dropis relevant to actually drop nonce values for the particular frontend site.