test(workerd): reproduce stacked content-encoding decode gap - #2986
Draft
james-elicx wants to merge 1 commit into
Draft
test(workerd): reproduce stacked content-encoding decode gap#2986james-elicx wants to merge 1 commit into
james-elicx wants to merge 1 commit into
Conversation
commit: |
Contributor
|
Contributor
Performance benchmarksCompared 0 improved · 0 regressed · 6 within ±1.5%
View detailed results and traces 🟢 improvement · 🔴 regression · ⚫ change below 1.5% · paired base/head |
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
gzipcontrol with a genuinely double-gzippedgzip, gzipresponseencodeResponseBody: "manual"and Node native Fetch as behavioral controlsObserved
With Wrangler 4.124.0, the single-gzip response decodes to JSON. The default stacked response remains encoded, begins with gzip magic bytes (
1f8b), and fails JSON parsing exactly like explicit manual mode. Node native Fetch decodes both responses successfully.Validation
node --check origin.mjs worker.js node-baseline.mjswrangler dev+curlreproductionnode node-baseline.mjsnpx --yes wrangler@4.124.0 deploy --dry-runDraft handoff for the Workerd runtime team; no vinext, Next.js, OpenNext, cache backend, account, or deployment is involved.