#109704theme-camino: usage of theme breaks cache-control header
Description
When using typo3/theme-camino the cache-control header is always set to “private, no-store” ignoring default and page-property cache settings.
Replacing theme-camino with bootstrap-package: caching works again.
Seems like a bug. Or is this intentional, if so – why?
Reviews 1
History 35
-
Georg Ringer changed assigned to Georg Ringer <span data-processor="relativetime" data-value="2026-04-23T15:52:12+00:00" > 04/23/26, 15:52 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 93833 status
NewUnder Review <span data-processor="relativetime" data-value="2026-04-23T17:23:55+00:00" > 04/23/26, 17:23 </span> -
Gerrit Code Review pushed patch set 2 for main to change 93833 <span data-processor="relativetime" data-value="2026-05-05T02:49:08+00:00" > 05/05/26, 02:49 </span>
-
Georg Ringer commented and changed status
Under ReviewClosed <span data-processor="relativetime" data-value="2026-08-27T16:47:58+00:00" > 08/27/26, 16:47 </span> -
Thomas Kaiser commented <span data-processor="relativetime" data-value="2026-08-28T11:24:22+00:00" > 08/28/26, 11:24 </span>
sorry for the late response!
I see the reasoning and think it’s valid from a developer point of view. Yet, this leaves no way to use Camino & client-side caching without extra configuration, wich is a bit sad and a violation of the “ready-to-use” purpose/promise of the theme, as I understood it. Don’t know if that’s worth another go at solving the issue in a different way.
thanks for creating the issue. closing it with the reasons given in the comments, see https://docs.typo3.org/c/typo3/cms-core/main/en-us/Changelog/13.3/Feature-104914-UpdatedHTTPHeadersForFrontendRenderingAndNewTypoScriptSettingForProxies.html
> Thus, config.sendCacheHeaders = 1 should be used with extreme care.
as integrator you can use that knowing the consequences