mirror of
https://github.com/nodejs/node.git
synced 2025-05-07 15:35:41 +00:00
c30ef3cbd2
Timing out and closing the socket after two minutes have elapsed is surprising and problematic for users. This behavior was specific to Node.js, and doesn't seem to be common in other language runtimes. Fixes: https://github.com/nodejs/node/issues/27556 PR-URL: https://github.com/nodejs/node/pull/27558 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Rich Trott <rtrott@gmail.com>
51 lines
1.3 KiB
JavaScript
51 lines
1.3 KiB
JavaScript
'use strict';
|
|
|
|
const common = require('../common');
|
|
if (!common.hasIPv6)
|
|
common.skip('IPv6 support required');
|
|
|
|
const initHooks = require('./init-hooks');
|
|
const verifyGraph = require('./verify-graph');
|
|
const http = require('http');
|
|
|
|
const hooks = initHooks();
|
|
hooks.enable();
|
|
|
|
const server = http.createServer(common.mustCall(function(req, res) {
|
|
res.end();
|
|
this.close(common.mustCall());
|
|
}));
|
|
server.listen(0, common.mustCall(function() {
|
|
http.get({
|
|
host: '::1',
|
|
family: 6,
|
|
port: server.address().port
|
|
}, common.mustCall());
|
|
}));
|
|
|
|
process.on('exit', function() {
|
|
hooks.disable();
|
|
|
|
verifyGraph(
|
|
hooks,
|
|
[ { type: 'TCPSERVERWRAP',
|
|
id: 'tcpserver:1',
|
|
triggerAsyncId: null },
|
|
{ type: 'TCPWRAP', id: 'tcp:1', triggerAsyncId: 'tcpserver:1' },
|
|
{ type: 'TCPCONNECTWRAP',
|
|
id: 'tcpconnect:1',
|
|
triggerAsyncId: 'tcp:1' },
|
|
{ type: 'HTTPCLIENTREQUEST',
|
|
id: 'httpclientrequest:1',
|
|
triggerAsyncId: 'tcpserver:1' },
|
|
{ type: 'TCPWRAP', id: 'tcp:2', triggerAsyncId: 'tcpserver:1' },
|
|
{ type: 'Timeout', id: 'timeout:1', triggerAsyncId: 'tcp:2' },
|
|
{ type: 'HTTPINCOMINGMESSAGE',
|
|
id: 'httpincomingmessage:1',
|
|
triggerAsyncId: 'tcp:2' },
|
|
{ type: 'SHUTDOWNWRAP',
|
|
id: 'shutdown:1',
|
|
triggerAsyncId: 'tcp:2' } ]
|
|
);
|
|
});
|