From 90c79e1b35849b126fa59952fa2bd6eb81c97286 Mon Sep 17 00:00:00 2001
From: Luigi Pinca <luigipinca@gmail.com>
Date: Tue, 12 Apr 2022 10:17:25 +0200
Subject: [PATCH] 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.
---
 doc/api/http.md | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/doc/api/http.md b/doc/api/http.md
index 5c3c7d9a7a7180..b884305e3a5e08 100644
--- a/doc/api/http.md
+++ b/doc/api/http.md
@@ -438,6 +438,15 @@ deprecated:
 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
@@ -523,6 +532,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