doc: fix wrong response.end() at request.socket
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:
parent
710110788b
commit
019a2c4f84
@ -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:
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user