-
-
Notifications
You must be signed in to change notification settings - Fork 745
feat: add configurable maxPayloadSize for WebSocket #4955
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
mcollina
wants to merge
3
commits into
main
Choose a base branch
from
feature/configurable-max-decompressed-message-size
base: main
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
Show all changes
3 commits
Select commit
Hold shift + click to select a range
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,117 @@ | ||
| 'use strict' | ||
|
|
||
| const { test } = require('node:test') | ||
| const { once } = require('node:events') | ||
| const { WebSocketServer } = require('ws') | ||
| const { WebSocket, Agent, Client, Pool } = require('../..') | ||
|
|
||
| test('Agent webSocketOptions.maxPayloadSize is read correctly', async (t) => { | ||
| const customLimit = 128 * 1024 * 1024 // 128 MB | ||
| const agent = new Agent({ | ||
| webSocket: { | ||
| maxPayloadSize: customLimit | ||
| } | ||
| }) | ||
|
|
||
| t.after(() => agent.close()) | ||
|
|
||
| // Verify the option is stored and retrievable | ||
| t.assert.strictEqual(agent.webSocketOptions.maxPayloadSize, customLimit) | ||
| }) | ||
|
|
||
| test('Agent with default webSocketOptions uses 64 MB limit', async (t) => { | ||
| const agent = new Agent() | ||
|
|
||
| t.after(() => agent.close()) | ||
|
|
||
| // Default should be 64 MB | ||
| t.assert.strictEqual(agent.webSocketOptions.maxPayloadSize, 64 * 1024 * 1024) | ||
| }) | ||
|
|
||
| test('Custom maxPayloadSize allows messages under limit', async (t) => { | ||
| const server = new WebSocketServer({ | ||
| port: 0, | ||
| perMessageDeflate: true | ||
| }) | ||
|
|
||
| t.after(() => server.close()) | ||
| await once(server, 'listening') | ||
|
|
||
| const dataSize = 512 * 1024 // 512 KB | ||
|
|
||
| server.on('connection', (ws) => { | ||
| ws.send(Buffer.alloc(dataSize, 0x41), { binary: true }) | ||
| }) | ||
|
|
||
| // Set custom limit of 1 MB via Agent | ||
| const agent = new Agent({ | ||
| webSocket: { | ||
| maxPayloadSize: 1 * 1024 * 1024 | ||
| } | ||
| }) | ||
|
|
||
| t.after(() => agent.close()) | ||
|
|
||
| const client = new WebSocket(`ws://127.0.0.1:${server.address().port}`, { dispatcher: agent }) | ||
|
|
||
| const [event] = await once(client, 'message') | ||
| t.assert.strictEqual(event.data.size, dataSize, 'Message under limit should be received') | ||
| client.close() | ||
| }) | ||
|
|
||
| test('Messages at exactly the limit succeed', async (t) => { | ||
| const limit = 1 * 1024 * 1024 // 1 MB | ||
| const server = new WebSocketServer({ | ||
| port: 0, | ||
| perMessageDeflate: true | ||
| }) | ||
|
|
||
| t.after(() => server.close()) | ||
| await once(server, 'listening') | ||
|
|
||
| server.on('connection', (ws) => { | ||
| ws.send(Buffer.alloc(limit, 0x41), { binary: true }) | ||
| }) | ||
|
|
||
| const agent = new Agent({ | ||
| webSocket: { | ||
| maxPayloadSize: limit | ||
| } | ||
| }) | ||
|
|
||
| t.after(() => agent.close()) | ||
|
|
||
| const client = new WebSocket(`ws://127.0.0.1:${server.address().port}`, { dispatcher: agent }) | ||
|
|
||
| const [event] = await once(client, 'message') | ||
| t.assert.strictEqual(event.data.size, limit, 'Message at exactly the limit should succeed') | ||
| client.close() | ||
| }) | ||
|
|
||
| test('Client webSocketOptions.maxPayloadSize is read correctly', async (t) => { | ||
| const customLimit = 32 * 1024 * 1024 // 32 MB | ||
| const client = new Client('http://localhost', { | ||
| webSocket: { | ||
| maxPayloadSize: customLimit | ||
| } | ||
| }) | ||
|
|
||
| t.after(() => client.close()) | ||
|
|
||
| // Verify the option is stored and retrievable | ||
| t.assert.strictEqual(client.webSocketOptions.maxPayloadSize, customLimit) | ||
| }) | ||
|
|
||
| test('Pool webSocketOptions.maxPayloadSize is read correctly', async (t) => { | ||
| const customLimit = 16 * 1024 * 1024 // 16 MB | ||
| const pool = new Pool('http://localhost', { | ||
| webSocket: { | ||
| maxPayloadSize: customLimit | ||
| } | ||
| }) | ||
|
|
||
| t.after(() => pool.close()) | ||
|
|
||
| // Verify the option is stored and retrievable | ||
| t.assert.strictEqual(pool.webSocketOptions.maxPayloadSize, customLimit) | ||
| }) |
Oops, something went wrong.
Oops, something went wrong.
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.
Nit: It might be better to validate the size as soon as the length is determined—whether it's the immediate 0-125 value or the subsequent 16/64-bit extended fields. This prevents us from proceeding to READ_DATA and wasting bandwidth on a request that's bound to fail. It feels a bit odd to wait for the actual data to arrive when the length from the header already provides sufficient grounds for rejection.