http: fix keep-alive socket reuse race in requestOnFinish#61710
Closed
martinslota wants to merge 5 commits intonodejs:mainfrom
Closed
http: fix keep-alive socket reuse race in requestOnFinish#61710martinslota wants to merge 5 commits intonodejs:mainfrom
requestOnFinish#61710martinslota wants to merge 5 commits intonodejs:mainfrom
Conversation
Collaborator
|
Review requested:
|
Open
3 tasks
Contributor
Author
|
The fix can also be backported to Node.js versions 19 and upwards. |
756f872 to
4802f3a
Compare
When the HTTP response ends before the request's 'finish' event fires, responseOnEnd() and requestOnFinish() can both call responseKeepAlive(), corrupting the socket that the agent may have already handed to another request. This commit adds a !req.destroyed guard to requestOnFinish() so the second call is skipped when the socket has already been released. Fixes: nodejs#60001
4802f3a to
52c3851
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #61710 +/- ##
==========================================
- Coverage 89.74% 89.73% -0.01%
==========================================
Files 675 675
Lines 204601 204605 +4
Branches 39319 39317 -2
==========================================
- Hits 183611 183610 -1
+ Misses 13275 13270 -5
- Partials 7715 7725 +10
🚀 New features to boost your workflow:
|
pimterry
approved these changes
Feb 9, 2026
Member
pimterry
left a comment
There was a problem hiding this comment.
LGTM 👍 Nice work on a tricky edge case @martinslota
Collaborator
Contributor
Author
|
Looks like some checks have failed - some of them related to an event loop delay test (example): I'm not really sure how to fix that. |
Collaborator
Member
|
Not to worry I strongly suspect that's a flaky test @martinslota, I've re-run the failures. |
Collaborator
metcoder95
approved these changes
Feb 10, 2026
pimterry
pushed a commit
that referenced
this pull request
Feb 13, 2026
When the HTTP response ends before the request's 'finish' event fires, responseOnEnd() and requestOnFinish() can both call responseKeepAlive(), corrupting the socket that the agent may have already handed to another request. This commit adds a !req.destroyed guard to requestOnFinish() so the second call is skipped when the socket has already been released. Fixes: #60001 PR-URL: #61710 Reviewed-By: Tim Perry <pimterry@gmail.com>
Member
|
Landed in 37ff1ea |
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.
When the response ends before the request's
'finish'event fires,responseOnEnd()andrequestOnFinish()can both callresponseKeepAlive(), corrupting the socket that the agent may have already handed to another request.This PR adds a
!req.destroyedguard torequestOnFinish()so the second call is skipped when the socket has already been released.Fixes #60001.
Relates to aws/aws-sdk-js-v3#6426.