Open
Conversation
…ing headers (testing fix for CVE-2026-40073)
|
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.
closes # CVE-2026-40073
When reviewing the fix for the body size limit bypass in the node adapter,
I noticed the existing test suite only covered the updated code paths
(chunked encoding, valid Content-Length) but not the original bypass path.
This adds a test documenting that HTTP/1.1 requests with no
Content-Lengthand no
Transfer-Encodingheader return an empty body rather than processingoversized input.
Tests
pnpm test...Changesets
Edits