From e733af67ac4d7f53851ec2a31cd73fe749eced2c Mon Sep 17 00:00:00 2001 From: Luigi Pinca Date: Tue, 20 Feb 2018 18:33:05 +0100 Subject: [PATCH] doc: update description of 'clientError' event Default behavior is to send a '400 Bad Request' response if the socket is writable. Refs: https://github.com/nodejs/node/pull/15324 --- doc/api/http.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/api/http.md b/doc/api/http.md index daa058a8b0b426..7a29d95d677cae 100644 --- a/doc/api/http.md +++ b/doc/api/http.md @@ -784,10 +784,11 @@ changes: If a client connection emits an `'error'` event, it will be forwarded here. Listener of this event is responsible for closing/destroying the underlying -socket. For example, one may wish to more gracefully close the socket with an -HTTP '400 Bad Request' response instead of abruptly severing the connection. +socket. For example, one may wish to more gracefully close the socket with a +custom HTTP response instead of abruptly severing the connection. -Default behavior is to destroy the socket immediately on malformed request. +Default behavior is to close the socket with an HTTP '400 Bad Request' response +if possible, otherwise the socket is immediately destroyed. `socket` is the [`net.Socket`][] object that the error originated from.