1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: fix wrong response.end() at request.socket

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/19507
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Shigeki Ohtsu <ohtsu@ohtsu.org>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
This commit is contained in:
ikasumiwt 2018-04-13 01:31:03 +09:00 committed by Ruben Bridgewater
parent 710110788b
commit 019a2c4f84
No known key found for this signature in database
GPG Key ID: F07496B3EB3C1762
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/api/http.md
View File

@ -676,9 +676,8 @@ added: v0.3.0
Reference to the underlying socket. Usually users will not want to access Reference to the underlying socket. Usually users will not want to access
this property. In particular, the socket will not emit `'readable'` events this property. In particular, the socket will not emit `'readable'` events
because of how the protocol parser attaches to the socket. After because of how the protocol parser attaches to the socket. The `socket`
`response.end()`, the property is nulled. The `socket` may also be accessed may also be accessed via `request.connection`.
via `request.connection`.
Example: Example: