We have a max size of 20mb set since the servers we fetch from can sometimes give us an endless amount of data (I mean 12 hours of useless 300GB data endless! 😄).

Once the size limit is breached, node-fetch successfully throws an error, the promise is rejected — but the HTTP request isn't stopped, so everything appears fine.

That is until you suddenly see huge spikes in inbound traffic and CPU, and eventually realize a node process has been running for 12 hours instead of 12 seconds!

Is this part of the spec, or a bug? It feels like unexpected behavior to me.

Thanks!