node/test/parallel/test-http-no-read-no-dump.js
Robert Nagy e034f5c3d9
http: don't emit 'readable' after 'close'
PR-URL: https://github.com/nodejs/node/pull/32277
Refs: https://github.com/nodejs/node/issues/28710
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: James M Snell <jasnell@gmail.com>
2020-03-30 10:22:11 +02:00

58 lines
1.1 KiB
JavaScript

'use strict';
const common = require('../common');
const http = require('http');
let onPause = null;
const server = http.createServer((req, res) => {
if (req.method === 'GET')
return res.end();
res.writeHead(200);
res.flushHeaders();
req.on('close', common.mustCall(() => {
req.on('end', common.mustNotCall());
}));
req.connection.on('pause', () => {
res.end();
onPause();
});
}).listen(0, common.mustCall(() => {
const agent = new http.Agent({
maxSockets: 1,
keepAlive: true
});
const port = server.address().port;
const post = http.request({
agent,
method: 'POST',
port,
}, common.mustCall((res) => {
res.resume();
post.write(Buffer.alloc(16 * 1024).fill('X'));
onPause = () => {
post.end('something');
};
}));
/* What happens here is that the server `end`s the response before we send
* `something`, and the client thought that this is a green light for sending
* next GET request
*/
post.write('initial');
http.request({
agent,
method: 'GET',
port,
}, common.mustCall((res) => {
server.close();
res.connection.end();
})).end();
}));