Cache expiry does't seem to work if force response caching is set

Created on 30 January 2023, almost 2 years ago

Updated 1 February 2023, almost 2 years ago

I'm trying to debug a plugin for API Proxy where I want to cache API responses when the underlying API doesn't suggest a cache age itself.

Create an API proxy that proxies another API without cache control headers.
Configure it with Cache API responses on and a small TTL (say 30 seconds).
Hit the API proxy end point.
Locate the `cache_page` row in the database..
Notice the `expire` column is set to -1 (permanent).
Notice that multiple hits to the api_proxy route return cached responses.
Notice that flushing all caches removes the row.
Notice that hitting the route again repopulates the row with an expiry of -1 once more.

I'm not clear what is happening. I've tried various different configurations in the settings.

I see that setting TTL isn't expected to work with the page cache API. Indeed in this case it seems that page cache rows don't pick up an expiry based on what is set in the API proxy settings UI.
https://www.drupal.org/docs/drupal-apis/cache-api/cache-max-age#s-limita... →

TBD

TBD

TBD

TBD

🐛 Bug report

Status

Needs review

Version

2.0

Component

Code

Created by

🇦🇺Australia queenvictoria

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @queenvictoria
Comment almost 2 years ago →
🇦🇺Australia queenvictoria
Status changed to Needs review almost 2 years ago3:49pm 1 February 2023
Comment almost 2 years ago →
🇪🇸Spain fran seva
Hi - we had the same issue and the problem seems to be the ttl is not being set correctly to cache max age.

Production build 0.71.5 2024