Skip to content

fix: set private Cache-Control for forced responses#124

Merged
Kikobeats merged 2 commits intomasterfrom
next
Mar 13, 2026
Merged

fix: set private Cache-Control for forced responses#124
Kikobeats merged 2 commits intomasterfrom
next

Conversation

@Kikobeats
Copy link
Copy Markdown
Owner

When forceExpiration is true, the response was emitted with Cache-Control: public, must-revalidate, max-age=0. The public directive allows CDNs (e.g. Cloudflare with Cache Everything) to store and serve stale copies even after expiration, preventing force from actually bypassing the CDN cache.

Use private, no-cache, no-store, max-age=0 instead so no shared cache can store a forced response.

Made-with: Cursor

When `forceExpiration` is true, the response was emitted with
`Cache-Control: public, must-revalidate, max-age=0`. The `public`
directive allows CDNs (e.g. Cloudflare with Cache Everything) to
store and serve stale copies even after expiration, preventing
force from actually bypassing the CDN cache.

Use `private, no-cache, no-store, max-age=0` instead so no shared
cache can store a forced response.

Made-with: Cursor
@Kikobeats Kikobeats merged commit 486e636 into master Mar 13, 2026
2 checks passed
@Kikobeats Kikobeats deleted the next branch March 13, 2026 16:53
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