Skip to content

Set short Cache-Control on release data endpoints - #2091

Open
nicwortel wants to merge 1 commit into
php:masterfrom
nicwortel:cache-control
Open

nicwortel wants to merge 1 commit into
php:masterfrom
nicwortel:cache-control

Conversation

@nicwortel

@nicwortel nicwortel commented Nov 19, 2026 •

Copy link
Copy Markdown

The machine-readable release endpoints (such as https://www.php.net/releases/index.php?json) sent no Cache-Control header, so BunnyCDN applied its 30-day default.
I could not find any indication that the cache is purged when a new version of the website gets deployed.

Clients polling for new releases add cache busters to get fresh data (example: https://github.com/docker-library/php/blob/b2d8ba085a7b04175b33e23c0e3603dd6b6e34a9/versions.sh#L50), which bypasses the cache entirely.

Pages that set their own header show edge ages within their TTL, so the CDN appears to respect the origin header.

I chose a TTL of 5 minutes, let me know if I should change that.

The machine-readable release endpoints sent no Cache-Control header, so BunnyCDN
applied its 30-day default.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant