|
|
|
'use strict';
|
|
|
|
const common = require('../common');
|
|
|
|
const assert = require('assert');
|
|
|
|
const http = require('http');
|
|
|
|
const net = require('net');
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
|
|
|
|
const tests = [];
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
|
|
|
|
function test(fn) {
|
|
|
|
if (!tests.length)
|
|
|
|
process.nextTick(run);
|
|
|
|
tests.push(fn);
|
|
|
|
}
|
|
|
|
|
|
|
|
function run() {
|
|
|
|
const fn = tests.shift();
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
if (fn) {
|
|
|
|
console.log('# %s', fn.name);
|
|
|
|
fn(run);
|
|
|
|
} else {
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
console.log('ok');
|
|
|
|
}
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
}
|
|
|
|
|
|
|
|
test(function serverTimeout(cb) {
|
|
|
|
let caughtTimeout = false;
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
process.on('exit', function() {
|
|
|
|
assert(caughtTimeout);
|
|
|
|
});
|
|
|
|
const server = http.createServer(function(req, res) {
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
// just do nothing, we should get a timeout event.
|
|
|
|
});
|
|
|
|
server.listen(common.mustCall(function() {
|
|
|
|
http.get({ port: server.address().port }).on('error', function() {});
|
|
|
|
}));
|
|
|
|
const s = server.setTimeout(50, function(socket) {
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
caughtTimeout = true;
|
|
|
|
socket.destroy();
|
|
|
|
server.close();
|
|
|
|
cb();
|
|
|
|
});
|
|
|
|
assert.ok(s instanceof http.Server);
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
});
|
|
|
|
|
|
|
|
test(function serverRequestTimeout(cb) {
|
|
|
|
let caughtTimeout = false;
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
process.on('exit', function() {
|
|
|
|
assert(caughtTimeout);
|
|
|
|
});
|
|
|
|
const server = http.createServer(function(req, res) {
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
// just do nothing, we should get a timeout event.
|
|
|
|
const s = req.setTimeout(50, function() {
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
caughtTimeout = true;
|
|
|
|
req.socket.destroy();
|
|
|
|
server.close();
|
|
|
|
cb();
|
|
|
|
});
|
|
|
|
assert.ok(s instanceof http.IncomingMessage);
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
});
|
|
|
|
server.listen(common.mustCall(function() {
|
|
|
|
const port = server.address().port;
|
|
|
|
const req = http.request({ port: port, method: 'POST' });
|
|
|
|
req.on('error', function() {});
|
|
|
|
req.write('Hello');
|
|
|
|
// req is in progress
|
|
|
|
}));
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
});
|
|
|
|
|
|
|
|
test(function serverResponseTimeout(cb) {
|
|
|
|
let caughtTimeout = false;
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
process.on('exit', function() {
|
|
|
|
assert(caughtTimeout);
|
|
|
|
});
|
|
|
|
const server = http.createServer(function(req, res) {
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
// just do nothing, we should get a timeout event.
|
|
|
|
const s = res.setTimeout(50, function() {
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
caughtTimeout = true;
|
|
|
|
res.socket.destroy();
|
|
|
|
server.close();
|
|
|
|
cb();
|
|
|
|
});
|
|
|
|
assert.ok(s instanceof http.OutgoingMessage);
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
});
|
|
|
|
server.listen(common.mustCall(function() {
|
|
|
|
const port = server.address().port;
|
|
|
|
http.get({ port: port }).on('error', function() {});
|
|
|
|
}));
|
http: More useful setTimeout API on server
This adds the following to HTTP:
* server.setTimeout(msecs, callback)
Sets all new connections to time out after the specified time, at
which point it emits 'timeout' on the server, passing the socket as an
argument.
In this way, timeouts can be handled in one place consistently.
* req.setTimeout(), res.setTimeout()
Essentially an alias to req/res.socket.setTimeout(), but without
having to delve into a "buried" object. Adds a listener on the
req/res object, but not on the socket.
* server.timeout
Number of milliseconds before incoming connections time out.
(Default=1000*60*2, as before.)
Furthermore, if the user sets up their own timeout listener on either
the server, the request, or the response, then the default behavior
(destroying the socket) is suppressed.
Fix #3460
12 years ago
|
|
|
});
|
|
|
|
|
|
|
|
test(function serverRequestNotTimeoutAfterEnd(cb) {
|
|
|
|
let caughtTimeoutOnRequest = false;
|
|
|
|
let caughtTimeoutOnResponse = false;
|
|
|
|
process.on('exit', function() {
|
|
|
|
assert(!caughtTimeoutOnRequest);
|
|
|
|
assert(caughtTimeoutOnResponse);
|
|
|
|
});
|
|
|
|
const server = http.createServer(function(req, res) {
|
|
|
|
// just do nothing, we should get a timeout event.
|
|
|
|
const s = req.setTimeout(50, function(socket) {
|
|
|
|
caughtTimeoutOnRequest = true;
|
|
|
|
});
|
|
|
|
assert.ok(s instanceof http.IncomingMessage);
|
|
|
|
res.on('timeout', function(socket) {
|
|
|
|
caughtTimeoutOnResponse = true;
|
|
|
|
});
|
|
|
|
});
|
|
|
|
server.on('timeout', function(socket) {
|
|
|
|
socket.destroy();
|
|
|
|
server.close();
|
|
|
|
cb();
|
|
|
|
});
|
|
|
|
server.listen(common.mustCall(function() {
|
|
|
|
const port = server.address().port;
|
|
|
|
http.get({ port: port }).on('error', function() {});
|
|
|
|
}));
|
|
|
|
});
|
|
|
|
|
|
|
|
test(function serverResponseTimeoutWithPipeline(cb) {
|
|
|
|
let caughtTimeout = '';
|
|
|
|
process.on('exit', function() {
|
|
|
|
assert.strictEqual(caughtTimeout, '/2');
|
|
|
|
});
|
|
|
|
const server = http.createServer(function(req, res) {
|
|
|
|
const s = res.setTimeout(50, function() {
|
|
|
|
caughtTimeout += req.url;
|
|
|
|
});
|
|
|
|
assert.ok(s instanceof http.OutgoingMessage);
|
|
|
|
if (req.url === '/1') res.end();
|
|
|
|
});
|
|
|
|
server.on('timeout', function(socket) {
|
|
|
|
socket.destroy();
|
|
|
|
server.close();
|
|
|
|
cb();
|
|
|
|
});
|
|
|
|
server.listen(common.mustCall(function() {
|
|
|
|
const port = server.address().port;
|
|
|
|
const c = net.connect({ port: port, allowHalfOpen: true }, function() {
|
|
|
|
c.write('GET /1 HTTP/1.1\r\nHost: localhost\r\n\r\n');
|
|
|
|
c.write('GET /2 HTTP/1.1\r\nHost: localhost\r\n\r\n');
|
|
|
|
c.write('GET /3 HTTP/1.1\r\nHost: localhost\r\n\r\n');
|
|
|
|
});
|
|
|
|
}));
|
|
|
|
});
|
|
|
|
|
|
|
|
test(function idleTimeout(cb) {
|
|
|
|
let caughtTimeoutOnRequest = false;
|
|
|
|
let caughtTimeoutOnResponse = false;
|
|
|
|
let caughtTimeoutOnServer = false;
|
|
|
|
process.on('exit', function() {
|
|
|
|
assert(!caughtTimeoutOnRequest);
|
|
|
|
assert(!caughtTimeoutOnResponse);
|
|
|
|
assert(caughtTimeoutOnServer);
|
|
|
|
});
|
|
|
|
const server = http.createServer(function(req, res) {
|
|
|
|
req.on('timeout', function(socket) {
|
|
|
|
caughtTimeoutOnRequest = true;
|
|
|
|
});
|
|
|
|
res.on('timeout', function(socket) {
|
|
|
|
caughtTimeoutOnResponse = true;
|
|
|
|
});
|
|
|
|
res.end();
|
|
|
|
});
|
|
|
|
const s = server.setTimeout(50, function(socket) {
|
|
|
|
caughtTimeoutOnServer = true;
|
|
|
|
socket.destroy();
|
|
|
|
server.close();
|
|
|
|
cb();
|
|
|
|
});
|
|
|
|
assert.ok(s instanceof http.Server);
|
|
|
|
server.listen(common.mustCall(function() {
|
|
|
|
const port = server.address().port;
|
|
|
|
const c = net.connect({ port: port, allowHalfOpen: true }, function() {
|
|
|
|
c.write('GET /1 HTTP/1.1\r\nHost: localhost\r\n\r\n');
|
|
|
|
// Keep-Alive
|
|
|
|
});
|
|
|
|
}));
|
|
|
|
});
|