You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Also, it seems to me that all errors are emitted on the request object and never on the response object. Is the 'error' listener even useful on the response object?
I see that end emits from http.IncomingMessage(as a client response) in success case and when server closes connection as well (fail). Shouldn't be only close/aborted without end?
trivikr
added a commit
to trivikr/node
that referenced
this issue
Apr 15, 2018
Fixes: #20102Fixes: #20101Fixes: #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: #20075Fixes: #17352
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
The response object from
http.ClientRequest
only seems to amit a close event if the request was aborted?The text was updated successfully, but these errors were encountered: