Problem/Motivation

Currently when an object is read from the results cache, it has the max-age of the time it was written to the cache.

In combination with https://www.drupal.org/project/drupal/issues/2352009, it results in havig the same max-age header all the time. This can be problematic when using multiple varnish frontends for drupal.

Steps to reproduce

Proposed resolution

Re-calculate the the max-age after reading from cache.

Issue fork graphql-3586845

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

chr.fritsch created an issue. See original summary.

chr.fritsch opened merge request !85

kingdutch’s picture

kingdutch
he/him
Primary language English
commented
Assigned: Unassigned » kingdutch
Status: Active » Needs review
kingdutch’s picture

kingdutch
he/him
Primary language English
commented
Assigned: kingdutch » Unassigned
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

kingdutch’s picture

kingdutch
he/him
Primary language English
commented
Issue tags: +DevDaysAthens2026

Tag for statistics :)