Stop compressing resume data cache - #97241
Open
gnoff wants to merge 1 commit into
Open
Conversation
Contributor
Stats cancelledCommit: f503903 |
Contributor
Failing CI jobsCommit: f503903 | About building and testing Next.js |
gnoff
force-pushed
the
jstory/stop-compressing-rdc
branch
from
August 12, 2026 16:48
03eea21 to
abfe394
Compare
gnoff
changed the base branch from
canary
to
jstory/warn-large-uncompressed-rdc
August 12, 2026 16:49
gnoff
force-pushed
the
jstory/stop-compressing-rdc
branch
from
August 12, 2026 17:06
abfe394 to
ba3c3c8
Compare
gnoff
force-pushed
the
jstory/stop-compressing-rdc
branch
2 times, most recently
from
August 12, 2026 17:44
6fc1499 to
93c1bbf
Compare
gnoff
force-pushed
the
jstory/stop-compressing-rdc
branch
from
August 12, 2026 17:51
93c1bbf to
1e8a0ce
Compare
## Summary Serialize the Resume Data Cache in postponed state as raw JSON instead of a zlib-compressed base64 string. This lets cache persistence implementations decide whether and how to compress postponed state, and removes the decompression path and zip-bomb exposure from Next.js. Remove the temporary experimental.disableResumeDataCacheCompression rollout flag together with the deflate and inflate branches, making raw JSON the only persisted representation. The existing postponed-state request-body size limit remains in place. Parsing diagnostics and tests cover truncated or malformed JSON cache tails. ## Verification - pnpm build-all - pnpm exec jest packages/next/src/server/resume-data-cache/resume-data-cache.test.ts packages/next/src/server/app-render/postponed-state.test.ts --runInBand - pnpm --filter=next types <!-- NEXT_JS_LLM -->
gnoff
force-pushed
the
jstory/stop-compressing-rdc
branch
from
August 12, 2026 18:05
1e8a0ce to
f503903
Compare
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
Serialize the Resume Data Cache in postponed state as raw JSON instead of a zlib-compressed base64 string. This lets cache persistence implementations decide whether and how to compress postponed state, and removes the decompression path and zip-bomb exposure from Next.js.
Remove the temporary
experimental.disableResumeDataCacheCompressionrollout flag together with the deflate and inflate branches, making raw JSON the only persisted representation.The existing postponed-state request-body size limit remains in place. Parsing diagnostics and tests cover truncated or malformed JSON cache tails.
This is the upper PR in a two-PR stack and should land after the lower rollout-control PR has had a canary observation period.
Verification
pnpm build-allpnpm exec jest packages/next/src/server/resume-data-cache/resume-data-cache.test.ts packages/next/src/server/app-render/postponed-state.test.ts --runInBandpnpm --filter=next types