Buffer streamed responses before edge caching#6
Merged
Conversation
Cache API rejects responses without Content-Length. TanStack Start streams HTML (chunked transfer), so cache.put() was silently failing. Now reads the full response body into an ArrayBuffer first.
gavdevs
added a commit
that referenced
this pull request
Apr 5, 2026
Buffer streamed responses before edge caching
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
1 participant
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
Content-LengthdefaultStreamHandlerwhich streams HTML (chunked transfer encoding)cache.put()from Use Cloudflare Cache API for actual edge caching #5 was silently failing on every requestarrayBuffer()before storing in edge cacheContext
Follow-up to #5 — edge caching still wasn't working because streamed responses can't be cached. This is why Turso reads stayed at 25M after the previous fix.