doc: document the 'close' and 'finish' events

These events are already documented as events of the `http.ServerResponse` class. Document that they can also be emitted on instances of the `http.ClientRequest` class. PR-URL: nodejs/node#42704 Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]> Reviewed-By: Akhil Marsonya <[email protected]> Reviewed-By: Mestery <[email protected]>
noslate-project · Oct 10, 2022 · f5c1ee2 · f5c1ee2
1 parent 7eb9c63
commit f5c1ee2
Showing 1 changed file with 20 additions and 0 deletions.
diff --git a/doc/api/http.md b/doc/api/http.md
@@ -434,6 +434,15 @@ deprecated: v16.12.0
 Emitted when the request has been aborted by the client. This event is only
 emitted on the first call to `abort()`.
 
+### Event: `'close'`
+
+<!-- YAML
+added: v0.5.4
+-->
+
+Indicates that the request is completed, or its underlying connection was
+terminated prematurely (before the response completion).
+
 ### Event: `'connect'`
 
 <!-- YAML
@@ -519,6 +528,17 @@ Emitted when the server sends a '100 Continue' HTTP response, usually because
 the request contained 'Expect: 100-continue'. This is an instruction that
 the client should send the request body.
 
+### Event: `'finish'`
+
+<!-- YAML
+added: v0.3.6
+-->
+
+Emitted when the request has been sent. More specifically, this event is emitted
+when the last segment of the response headers and body have been handed off to
+the operating system for transmission over the network. It does not imply that
+the server has received anything yet.
+
 ### Event: `'information'`
 
 <!-- YAML