Make `clientError` overridable by indutny · Pull Request #4557 · nodejs/node
added 2 commits
January 6, 2016 16:59`clientError` will have `http.Server`-specific behavior, and we don't want to shadow it in `tls.Server`.
Make default `clientError` behavior (close socket immediately)
overridable. With this APIs it is possible to write a custom error
handler, and to send, for example, a 400 HTTP response.
http.createServer(...).on('clientError', function(err, socket) {
socket.end('HTTP/1.1 400 Bad Request\r\n\r\n');
socket.destroy();
});
Fix: nodejs#4543
labels
Jan 6, 2016
vkurchatkin
removed
http
labels
Jan 6, 2016labels
Jan 6, 2016
vkurchatkin
added
tls
and removed tls
Issues and PRs related to the tls subsystem.labels
Jan 6, 2016indutny added a commit that referenced this pull request
Jan 7, 2016`clientError` will have `http.Server`-specific behavior, and we don't want to shadow it in `tls.Server`. PR-URL: #4557 Reviewed-By: Brian White <mscdex@mscdex.net>
indutny added a commit that referenced this pull request
Jan 7, 2016Make default `clientError` behavior (close socket immediately)
overridable. With this APIs it is possible to write a custom error
handler, and to send, for example, a 400 HTTP response.
http.createServer(...).on('clientError', function(err, socket) {
socket.end('HTTP/1.1 400 Bad Request\r\n\r\n');
socket.destroy();
});
Fix: #4543
PR-URL: #4557
Reviewed-By: Brian White <mscdex@mscdex.net>
This was referenced
Dec 7, 2023This was referenced
Dec 7, 2023This was referenced
Dec 7, 2023This was referenced
Dec 7, 2023This was referenced
Dec 8, 2023This was referenced
Dec 8, 2023This was referenced
Dec 8, 2023This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters