Repository navigation
fix: support raw ArrayBuffer in res.send (#7362) #7410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
OubaidaAwaw
wants to merge
1
commit into
expressjs:master
Choose a base branch
from
OubaidaAwaw:fix/arraybuffer-support-7362
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[P2] Keep normalizing typed-array views before ending the response
This branch skips the existing
Buffer.from(chunk, encoding)conversion for every view, not just the newly supported rawArrayBuffer. With the default app settings,res.send(new Uint16Array([0x0102, 0x0304]))previously returned 200 with bytes[2, 4]; it now reachesServerResponse.end()with aUint16Arrayand throwsERR_INVALID_ARG_TYPE, producing a 500. Node's response writer acceptsUint8Array/Buffer, but notUint16ArrayorInt16Array.Please preserve the view-to-Buffer conversion before calculating the final length and sending. This also prevents HEAD from advertising
Content-Length: 4for the previously two-byte representation. The currentUint8Arraytest does not cover this regression.Automated review. Reproduced through real loopback HTTP on Node 24.18.0 against base
a371447and head542756f, with Buffer/Uint8Array controls.