response does not end, res.on('end') event never occurs

[ORESoftware]

I have this POST request.
It looks the response never ends for a HTTP POST to /coverage/client...
Is it my code, or is it perhaps that the response doesn't get ended on the part of the server?

I have this code:

         let options = {
          port: 3050,
          host: cdtHost,
          path: '/coverage/client',
          method: 'POST',
          headers: {
            'Content-Type': 'application/json',
          }
        };
        let req = http.request(options, function (res) {

          res.once('end', function () { 
            console.log('\nFinished sending coverage data.');   /// << res.once('end') never fires
            done();
          });

        });

Maybe it's my misuse, but it looks like

          res.once('end', function () { 
            console.log('\nFinished sending coverage data.');   /// << res.once('end') never fires
            done();
          });

will never fire, not sure why.

[gireeshpunathil]

can you also add a data listener (though dummy) :

res.on('data', function () {
  });

and check?

Excerpts from doc

If no 'response' handler is added, then the response will be entirely discarded. However, if a 'response' event handler is added, then the data from the response object must be consumed, either by calling response.read() whenever there is a 'readable' event, or by adding a 'data' handler, or by calling the .resume() method. Until the data is consumed, the 'end' event will not fire.

[ORESoftware]

huh, thanks, that is so bizarre. that worked, but that seems like a really bad bug, but I guess that's just the way streams work in node. Top 5 most unexpected things I have seen in Node!

[gireeshpunathil]

I don't know the design decisions behind this, but please consider this example:

var http = require('http');
let req = http.get('http://ww.google.com', function (res) {
  setTimeout(function() {
    res.on('data', function (d) {
      console.log(d.length);
    });
  },10000);
  res.on('end', function () { 
    console.log('done');
  });
});

A true event-driven system does not / cannot mandate the ordering of event registrations to follow the order of their occurrences. So the end handler invocation is preserved forever in expectation of a future data registration and event, lest invoking end handler when it 'ended' runs the risk of premature cleanup of data and its pertinent internal resources before a consumer arrives.

Given the premises and circumstances, do you think a better solution could have been possible?

/cc @bnoordhuis

[ORESoftware]

thanks!