-
Notifications
You must be signed in to change notification settings - Fork 30.1k
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
http2: treat non-EOF empty frames like other invalid frames #37875
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
fd15502
http2: fix setting options before handle exists
addaleax 515cab2
http2: treat non-EOF empty frames like other invalid frames
addaleax 752cb85
fixup! http2: fix setting options before handle exists
addaleax a087881
fixup! http2: fix setting options before handle exists
addaleax 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 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 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
Binary file not shown.
This file contains 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,39 @@ | ||
'use strict'; | ||
const common = require('../common'); | ||
if (!common.hasCrypto) | ||
common.skip('missing crypto'); | ||
const { readSync } = require('../common/fixtures'); | ||
const net = require('net'); | ||
const http2 = require('http2'); | ||
const { once } = require('events'); | ||
|
||
async function main() { | ||
const blobWithEmptyFrame = readSync('emptyframe.http2'); | ||
const server = net.createServer((socket) => { | ||
socket.end(blobWithEmptyFrame); | ||
}).listen(0); | ||
await once(server, 'listening'); | ||
|
||
for (const maxSessionInvalidFrames of [0, 2]) { | ||
const client = http2.connect(`http://localhost:${server.address().port}`, { | ||
maxSessionInvalidFrames | ||
}); | ||
const stream = client.request({ | ||
':method': 'GET', | ||
':path': '/' | ||
}); | ||
if (maxSessionInvalidFrames) { | ||
stream.on('error', common.mustNotCall()); | ||
client.on('error', common.mustNotCall()); | ||
} else { | ||
stream.on('error', common.mustCall()); | ||
client.on('error', common.mustCall()); | ||
} | ||
stream.resume(); | ||
await once(stream, 'end'); | ||
client.close(); | ||
} | ||
server.close(); | ||
} | ||
|
||
main().then(common.mustCall()); |
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.
Should invalid_frame_count be reset if valid frames come through? Pertaining to #37849, if an end server is sending EOF frames after every valid frame, would this solution only allow for single requests in a session?
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.
So... I don't think we'd want to reset after every valid frame, or at least I think that would be a bit separate from this PR.
What would makes sense to me is to make this a ratio of invalid frames/total frames that is being limited, rather than the total # of invalid frames ... but that feels a bit out of scope here :/ In any case, users who do wish to allow for a large number of invalid frames can set the
maxSessionInvalidFrames
option to a large value, if they are connecting to problematic servers.