http: client request req & res 'close' order is inconsistent #20102
Labels
http
Issues or PRs related to the http subsystem.
Comments
ronag
added a commit
to nxtedition/node
that referenced
this issue
Apr 27, 2018
Fixes: nodejs#20102 Fixes: nodejs#20101 Fixes: nodejs#1735 - Response should always emit close. - Response should always emit aborted if aborted. - Response should always emit close after request has emitted close.
addaleax
pushed a commit
that referenced
this issue
May 14, 2018
Fixes: #20102 Fixes: #20101 Fixes: #1735 - Response should always emit close. - Response should always emit aborted if aborted. - Response should always emit close after request has emitted close. PR-URL: #20075 Fixes: #17352 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The order in which
closeis emitted on thehttp.ClientRequestrequest and response object is inconsistent depending on the situation.See e2e18ae and #20075
The text was updated successfully, but these errors were encountered: