Repository navigation
http - http.ClientRequest doesn't emit 'aborted'? #15259
Description
Activity
- changed the title
[-]HTTP request 'aborted'[/-][+]HTTP request missing 'aborted'[/+]on Sep 8, 2017 - changed the title
[-]HTTP request missing 'aborted'[/-][+]HTTP request missing 'aborted' event[/+]on Sep 8, 2017 - changed the title
[-]HTTP request missing 'aborted' event[/-][+] http.ClientRequest doesn't emit 'aborted'?[/+]on Sep 8, 2017 Yes, it's incorrect. It may have been copy/pasted from
http.IncomingMessage, which does emit it.- changed the title
[-] http.ClientRequest doesn't emit 'aborted'?[/-][+]http - http.ClientRequest doesn't emit 'aborted'?[/+]on Sep 8, 2017 The documentation for this event should be moved tohttp.ServerResponse.Edit: nvm.
- added a commit that references this issue
on Sep 19, 2017 - added a commit that references this issue
on Sep 23, 2017 - added a commit that references this issue
on Sep 25, 2017 - added a commit that references this issue
on Oct 17, 2017 - added a commit that references this issue
on Oct 25, 2017 - added a commit that references this issue
on Jul 27, 2026
Looking through the _http_client.js code it seems to me that the
http.ClientRequestobject never emits an ´aborted´ event (onlyclose). It's just the response object that emits theabortedevent.https://github.com/nodejs/node/blob/master/lib/_http_client.js#L366
That seems to go against the docs, https://nodejs.org/api/http.html#http_event_aborted