(server, socket, parser, state, ret)
| 952 | } |
| 953 | |
| 954 | function onParserExecute(server, socket, parser, state, ret) { |
| 955 | // When underlying `net.Socket` instance is consumed - no |
| 956 | // `data` events are emitted, and thus `socket.setTimeout` fires the |
| 957 | // callback even if the data is constantly flowing into the socket. |
| 958 | // See, https://github.com/nodejs/node/commit/ec2822adaad76b126b5cccdeaa1addf2376c9aa6 |
| 959 | socket._unrefTimer(); |
| 960 | debug('SERVER socketOnParserExecute %d', ret); |
| 961 | onParserExecuteCommon(server, socket, parser, state, ret, undefined); |
| 962 | } |
| 963 | |
| 964 | function onParserTimeout(server, socket) { |
| 965 | const serverTimeout = server.emit('timeout', socket); |
nothing calls this directly
no test coverage detected
searching dependent graphs…