Skip to content

Commit e9ad526

Browse files
lpincaBethGriggs
authored andcommittedFeb 12, 2019
doc: fix order of events when request is aborted
PR-URL: #24779 Reviewed-By: Anna Henningsen <[email protected]> Reviewed-By: Daniel Bevenius <[email protected]> Reviewed-By: Trivikram Kamat <[email protected]>
1 parent 16a1f96 commit e9ad526

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed
 

‎doc/api/http.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -2081,9 +2081,9 @@ will be emitted in the following order:
20812081
* `'socket'`
20822082
* (`req.abort()` called here)
20832083
* `'abort'`
2084-
* `'close'`
20852084
* `'error'` with an error with message `'Error: socket hang up'` and code
20862085
`'ECONNRESET'`
2086+
* `'close'`
20872087

20882088
If `req.abort()` is called after the response is received, the following events
20892089
will be emitted in the following order:
@@ -2093,10 +2093,10 @@ will be emitted in the following order:
20932093
* `'data'` any number of times, on the `res` object
20942094
* (`req.abort()` called here)
20952095
* `'abort'`
2096+
* `'aborted'` on the `res` object
20962097
* `'close'`
2097-
* `'aborted'` on the `res` object
2098-
* `'end'` on the `res` object
2099-
* `'close'` on the `res` object
2098+
* `'end'` on the `res` object
2099+
* `'close'` on the `res` object
21002100

21012101
Note that setting the `timeout` option or using the `setTimeout()` function will
21022102
not abort the request or do anything besides add a `'timeout'` event.

0 commit comments

Comments
 (0)