Use Cloudflare Cache API for actual edge caching#5
Merged
gavyncaldwell merged 1 commit intomainfrom Mar 13, 2026
Merged
Conversation
s-maxage headers alone do nothing on Workers — responses bypass Cloudflare's HTTP cache by default. Now explicitly storing responses in edge cache via caches.default, same pattern as icon proxy. Covers all page routes, sitemaps, and robots.txt.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
s-maxageheaders alone do nothing on Workers — responses bypass Cloudflare's HTTP cache by defaultcaches.default.put(), same pattern already used by icon proxyContext
After deploying the 1-week cache TTLs in #3, Turso reads were still at 25M because the cache headers weren't being read by anything — every request was still hitting the worker and Turso. This is the actual fix.