From fbf9e0609bdf390b6b9da5a574533fa3f2641ce3 Mon Sep 17 00:00:00 2001 From: ikasumiwt Date: Fri, 13 Apr 2018 01:31:03 +0900 Subject: [PATCH] doc: fix wrong response.end() at request.socket PR-URL: https://github.com/nodejs/node/pull/19507 Reviewed-By: Luigi Pinca Reviewed-By: James M Snell Reviewed-By: Shigeki Ohtsu Reviewed-By: Matteo Collina Reviewed-By: Trivikram Kamat Reviewed-By: Ruben Bridgewater --- doc/api/http.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/doc/api/http.md b/doc/api/http.md index cbedf8c99b07d3..eb5eb6b2dbb662 100644 --- a/doc/api/http.md +++ b/doc/api/http.md @@ -676,9 +676,8 @@ added: v0.3.0 Reference to the underlying socket. Usually users will not want to access this property. In particular, the socket will not emit `'readable'` events -because of how the protocol parser attaches to the socket. After -`response.end()`, the property is nulled. The `socket` may also be accessed -via `request.connection`. +because of how the protocol parser attaches to the socket. The `socket` +may also be accessed via `request.connection`. Example: