From a5b43e940497c31a1bf2fa40fdcd62551994babb Mon Sep 17 00:00:00 2001
From: Dr <dr@dr.run>
Date: Sun, 27 Dec 2020 20:45:36 +0800
Subject: [PATCH] doc: document http.IncomingMessage behaviour change

Add to the history table that the `destroyed` value returns `true` after
the incoming data is consumed.

Refs: https://github.com/nodejs/node/issues/36617
Refs: https://github.com/nodejs/node/pull/33035

PR-URL: https://github.com/nodejs/node/pull/36641
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Robert Nagy <ronagy@icloud.com>
---
 doc/api/http.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/doc/api/http.md b/doc/api/http.md
index ad34b6e1e7df40..df9247b670921b 100644
--- a/doc/api/http.md
+++ b/doc/api/http.md
@@ -1906,6 +1906,10 @@ the request body should be sent.
 <!-- YAML
 added: v0.1.17
 changes:
+  - version: v15.5.0
+    pr-url: https://github.com/nodejs/node/pull/33035
+    description: The `destroyed` value returns `true` after the incoming data
+                 is consumed.
   - version:
      - v13.1.0
      - v12.16.0
@@ -1920,6 +1924,11 @@ An `IncomingMessage` object is created by [`http.Server`][] or
 and [`'response'`][] event respectively. It may be used to access response
 status, headers and data.
 
+Different from it's `socket` value which is a subclass of {stream.Duplex}, the
+`IncomingMessage` itself extends {stream.Readable} and is created separately to
+parse and emit the incoming HTTP headers and payload, as the underlying socket
+may be reused multiple times in case of keep-alive.
+
 ### Event: `'aborted'`
 <!-- YAML
 added: v0.3.8