Module set cache max-age to 0 on every page as soon as user is authenticated

Created on 23 June 2025, 9 days ago

Problem/Motivation

The frontendpublishing module set a cache max-cache of 0 to all pages, as soon as a user is authenticated.

As a result the dynamic page cache is not called and website performance are impacted.

The code has not changed since years, which probably means the core behaviour of the cacheable metadata has been updated/fixed. But in any case it is now expected to do so, so we should focus on setting uncacheable page only where required (ex: only for use having frontendpublishing right ?)

Steps to reproduce

1. Install the module
2. Log in
3. Browse website and inspect response header: dynamic page cache is uncacheable (poor cacheability) and cache max-age is 0.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

📌 Task
Status

Active

Version

3.0

Component

Code

Created by

🇫🇷France GuillaumePacilly

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024