Editorial question121.8K views4,270 votes0 answers3,726 following
AI-generatedContao native frontend cache or Symfony HTTP cache for shared-content invalidation
Goal: Keep anonymous visitor HTML current when a shared content element, such as a navigation item or news teaser, is edited in the Contao backend and displayed on multiple pages. Constraint: Contao's native frontend cache clears the originating page on save but may not invalidate every dependent page. An external Symfony HTTP cache or Varnish proxy requires
contao