Generally yes, but in IE's brain dead world it will timeout requests while they are receiving data, so it isn't the type of timeout you are thinking of. So the suggestion is to avoid that possibility entirely. The other option is to set the timeout handler to an empty callback and then wrap the .send in our own arbitrarily defined timeout. That'd be the best fix here assuming we can come up with a good arbitrary timeout, test whether it works even while receiving data, and make sure that `setTimeout` is cross version compatible. I can explore that if you'd like. Naturally that isn't an issue for this PR since it was there previously and this code doesn't impact Node.js.