doc: fix order of events when request is aborted
PR-URL: https://github.com/nodejs/node/pull/24779 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
This commit is contained in:
parent
b5e9086c5a
commit
63469ed15c
@ -2075,9 +2075,9 @@ will be emitted in the following order:
|
||||
* `'socket'`
|
||||
* (`req.abort()` called here)
|
||||
* `'abort'`
|
||||
* `'close'`
|
||||
* `'error'` with an error with message `'Error: socket hang up'` and code
|
||||
`'ECONNRESET'`
|
||||
* `'close'`
|
||||
|
||||
If `req.abort()` is called after the response is received, the following events
|
||||
will be emitted in the following order:
|
||||
@ -2087,10 +2087,10 @@ will be emitted in the following order:
|
||||
* `'data'` any number of times, on the `res` object
|
||||
* (`req.abort()` called here)
|
||||
* `'abort'`
|
||||
* `'aborted'` on the `res` object
|
||||
* `'close'`
|
||||
* `'aborted'` on the `res` object
|
||||
* `'end'` on the `res` object
|
||||
* `'close'` on the `res` object
|
||||
* `'end'` on the `res` object
|
||||
* `'close'` on the `res` object
|
||||
|
||||
Note that setting the `timeout` option or using the `setTimeout()` function will
|
||||
not abort the request or do anything besides add a `'timeout'` event.
|
||||
|
Loading…
x
Reference in New Issue
Block a user