From 681edbe75f3d8c695b0ed1f403021164ec69d46a Mon Sep 17 00:00:00 2001 From: Luigi Pinca Date: Wed, 1 Dec 2021 20:47:20 +0100 Subject: [PATCH] doc: specify that `message.socket` can be nulled The `socket` property of the `IncomingMessage` object is nulled on the server after calling `message.destroy()` and on the client after a request completes and the socket is kept alive. Fixes: https://github.com/nodejs/node/issues/41011 PR-URL: https://github.com/nodejs/node/pull/41014 Reviewed-By: James M Snell Reviewed-By: Robert Nagy --- doc/api/http.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/api/http.md b/doc/api/http.md index 722defc987d0c7..7139e04c9b15fc 100644 --- a/doc/api/http.md +++ b/doc/api/http.md @@ -2313,7 +2313,7 @@ client's authentication details. This property is guaranteed to be an instance of the {net.Socket} class, a subclass of {stream.Duplex}, unless the user specified a socket -type other than {net.Socket}. +type other than {net.Socket} or internally nulled. ### `message.statusCode`