我正在运行一个 node.js 服务器 A,它使用 superagent 向另一个服务器 B 发出 HTTP 请求。
我调查了服务器 B 上的请求并看到了标头connection
being close
和 httpVersion 是1.1
:
var http = require('http');
var request = require('superagent');
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.write('req.httpVersion seen on server:' + req.httpVersion);
res.write('\nreq.headers.connection seen on server:' + req.headers.connection);
res.end();
}).listen(1337, '0.0.0.0');
request
.get('localhost:1337/helloword')
.end(function (err, res) {
console.log(res.text);
});
这导致:
req.httpVersion seen on server:1.1
req.headers.connection seen on server:close
但是,如果我从浏览器访问同一服务器,我会得到:
req.httpVersion seen on server:1.1
req.headers.connection seen on server:keep-alive
From https://www.rfc-editor.org/rfc/rfc2616#page-172 https://www.rfc-editor.org/rfc/rfc2616#page-172我了解到keep-alive
是 HTTP 1.1 的默认值,除非使用另外声明Connection: close
.
所以,我的问题是:
- 为什么 Superagent / Node.js 显式设置请求不使用 keep-alive / 持久连接?
- 如何强制 Superagent / Node.js 使用保持活动连接?
- 我如何进一步影响确切的行为(要保持打开的连接数、超时等)?
它似乎没有记录,但您可以使用以下功能将 http 代理传递给 superagentagent
。
因此,您可以使用此模块创建一个保持活动代理:https://www.npmjs.org/package/agentkeepalive https://www.npmjs.org/package/agentkeepalive并将其传递给超级代理。
像这样的事情:
util = require('util');
util.debuglog = require('debuglog');
var http = require('http');
var request = require('superagent');
var Agent = require('agentkeepalive');
var keepaliveAgent = new Agent({
maxSockets: 100,
maxFreeSockets: 10,
timeout: 60000,
keepAliveTimeout: 30000 // free socket keepalive for 30 seconds
});
http.createServer(function (req, res) {
res.writeHead(200, {'Content-Type': 'text/plain'});
res.write('req.httpVersion seen on server:' + req.httpVersion);
res.write('\nreq.headers.connection seen on server:' + req.headers.connection);
res.end();
}).listen(1337, '0.0.0.0');
request
.get('localhost:1337/helloword')
.agent(keepaliveAgent)
.end(function (err, res) {
console.log(res.text);
});
本文内容由网友自发贡献,版权归原作者所有,本站不承担相应法律责任。如您发现有涉嫌抄袭侵权的内容,请联系:hwhale#tublm.com(使用前将#替换为@)