From 38a5715c1ab23ff3bfde6f5ecc5fc0995d8209f0 Mon Sep 17 00:00:00 2001 From: Luigi Pinca Date: Thu, 1 Oct 2020 10:43:13 +0200 Subject: [PATCH] doc: avoid using deprecated connection property `request.connection` and `response.connection` are deprecated. Use `request.socket` and `response.socket` instead. PR-URL: https://github.com/nodejs/node/pull/35439 Reviewed-By: Anna Henningsen Reviewed-By: Pranshu Srivastava Reviewed-By: Harshitha K P Reviewed-By: Rich Trott Reviewed-By: Colin Ihrig Reviewed-By: James M Snell Reviewed-By: Gireesh Punathil Reviewed-By: Trivikram Kamat --- doc/api/http.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/doc/api/http.md b/doc/api/http.md index 9b48d18dff5c1f..79af82c1352924 100644 --- a/doc/api/http.md +++ b/doc/api/http.md @@ -923,8 +923,7 @@ 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. The `socket` -may also be accessed via `request.connection`. +because of how the protocol parser attaches to the socket. ```js const http = require('http'); @@ -1154,7 +1153,7 @@ This event is emitted when a new TCP stream is established. `socket` is typically an object of type [`net.Socket`][]. Usually users will not want to access this event. In particular, the socket will not emit `'readable'` events because of how the protocol parser attaches to the socket. The `socket` can -also be accessed at `request.connection`. +also be accessed at `request.socket`. This event can also be explicitly emitted by users to inject connections into the HTTP server. In that case, any [`Duplex`][] stream can be passed. @@ -1655,8 +1654,7 @@ 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 `response.connection`. +`response.end()`, the property is nulled. ```js const http = require('http'); @@ -2056,7 +2054,7 @@ added: v0.5.9 * `callback` {Function} * Returns: {http.IncomingMessage} -Calls `message.connection.setTimeout(msecs, callback)`. +Calls `message.socket.setTimeout(msecs, callback)`. ### `message.socket`