HTTP IncomingMessage (response) complete property is false

[kadler15]

Not sure how much of this is mocked as part of this library, but I noticed that the complete property on the response to a http request remains false, even after the entire reply message is received by the client (data and end events handled). E.g.:

nock('http://test.com')
  .replyDate()
  .defaultReplyHeaders({
    'Content-Type': 'application/text',
    'Content-Length': function(req, res, body) { return body.length; },
  })
  .get('/testFile.txt')
  .reply(200, Buffer.from(new Array(10000).fill('a')));

http.request({
  method: 'GET',
  url: 'http://test.com/testFile.txt'
  host: 'test.com',
  path: '/testFile.txt'
}, function(response) {
  const data = []
  response.on('data', function(chunk) { data.push(chunk); });
  response.on('end', function() {
    if (!response.complete) {
      console.log('Connection terminated while the message was being sent');  // <-- The case with nock
    } else {
      console.log('Entire message received');
    }
  });
});

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We try to do our best, but nock is maintained by volunteers and there is only so much we can do at a time. Thank you for your contributions.

[nockbot]

🎉 This issue has been resolved in version 11.0.0-beta.24 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[nockbot]

🎉 This issue has been resolved in version 11.0.0 🎉

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot 📦🚀