From 7aa7be0a493b44ab2e7bd9443d40958e9715d647 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcin=20Goli=C5=84ski?= Date: Thu, 3 Sep 2015 16:10:24 +0200 Subject: [PATCH] http.IncomingMessage: fix forgotten 'message' to 'socket' --- doc/api/http.markdown | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/api/http.markdown b/doc/api/http.markdown index 8ac89b1f388a59..bb115f7e340b53 100644 --- a/doc/api/http.markdown +++ b/doc/api/http.markdown @@ -92,7 +92,7 @@ When a new TCP stream is established. `socket` is 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`. +accessed at `request.socket`. ### Event: 'close' @@ -1020,7 +1020,7 @@ received. Only populated at the 'end' event. * `msecs` {Number} * `callback` {Function} -Calls `message.connection.setTimeout(msecs, callback)`. +Calls `message.socket.setTimeout(msecs, callback)`. Returns `message`.