-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
Unhandled 'error'
event on aborted request
#36931
Comments
cc: @nodejs/http |
@ronag it's not that. The error is emitted after |
Might have been solved with #36863 |
Needs a regression test either way. |
#36863 fixes this only if no agent is used. It does not fix the example in the issue description. |
ClientRequest could someone cause an unhandled error from socket. Fixes: nodejs#36931
ClientRequest could someone cause an unhandled error from socket. Fixes: #36931 PR-URL: #36970 Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Benjamin Gruenbaum <[email protected]>
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Always. No required condition.
What is the expected behavior?
The error is handled by the
'error'
event listener.What do you see instead?
The error is not handled.
Additional information
If
req.abort()
is removed the error is correctly handled.The text was updated successfully, but these errors were encountered: