-
Notifications
You must be signed in to change notification settings - Fork 29.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
http: keep HTTP/1.1 conns alive even if the Connection header is removed
Previously persistence was completed disabled if you removed this header, which is not correct for modern HTTP, where the header is optional and all connections should persist by default regardless. PR-URL: #46331 Reviewed-By: Matteo Collina <matteo.collina@gmail.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ricky Zhou <0x19951125@gmail.com>
- Loading branch information
Showing
2 changed files
with
75 additions
and
2 deletions.
There are no files selected for viewing
This file contains 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
72 changes: 72 additions & 0 deletions
72
test/parallel/test-http-remove-connection-header-persists-connection.js
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,72 @@ | ||
'use strict'; | ||
require('../common'); | ||
const assert = require('assert'); | ||
|
||
const net = require('net'); | ||
const http = require('http'); | ||
|
||
const server = http.createServer(function(request, response) { | ||
// When the connection header is removed, for HTTP/1.1 the connection should still persist. | ||
// For HTTP/1.0, the connection should be closed after the response automatically. | ||
response.removeHeader('connection'); | ||
|
||
response.end('beep boop\n'); | ||
}); | ||
|
||
const agent = new http.Agent({ keepAlive: true }); | ||
|
||
function makeHttp11Request(cb) { | ||
http.get({ | ||
port: server.address().port, | ||
agent | ||
}, function(res) { | ||
const socket = res.socket; | ||
|
||
assert.strictEqual(res.statusCode, 200); | ||
assert.strictEqual(res.headers.connection, undefined); | ||
|
||
res.setEncoding('ascii'); | ||
let response = ''; | ||
res.on('data', function(chunk) { | ||
response += chunk; | ||
}); | ||
res.on('end', function() { | ||
assert.strictEqual(response, 'beep boop\n'); | ||
|
||
// Wait till next tick to ensure that the socket is returned to the agent before | ||
// we continue to the next request | ||
process.nextTick(function() { | ||
cb(socket); | ||
}); | ||
}); | ||
}); | ||
} | ||
|
||
function makeHttp10Request(cb) { | ||
// We have to manually make HTTP/1.0 requests since Node does not allow sending them: | ||
const socket = net.connect({ port: server.address().port }, function() { | ||
socket.write('GET / HTTP/1.0\r\n' + | ||
'Host: localhost:' + server.address().port + '\r\n' + | ||
'\r\n'); | ||
socket.resume(); // Ignore the response itself | ||
|
||
setTimeout(function() { | ||
cb(socket); | ||
}, 10); | ||
}); | ||
} | ||
|
||
server.listen(0, function() { | ||
makeHttp11Request(function(firstSocket) { | ||
makeHttp11Request(function(secondSocket) { | ||
// Both HTTP/1.1 requests should have used the same socket: | ||
assert.strictEqual(firstSocket, secondSocket); | ||
|
||
makeHttp10Request(function(socket) { | ||
// The server should have immediately closed the HTTP/1.0 socket: | ||
assert.strictEqual(socket.closed, true); | ||
server.close(); | ||
}); | ||
}); | ||
}); | ||
}); |