Response write/end to noop() when request aborted about compression

[dougwilson]

The premise of the res.end and res.write to noop is flawed; it is 100% unnecessary. Because there was no investigation done in the original connect issue and no test proving it was necessary, it's hard to know, but I can only assume that those people were double-calling res.end() in their code, and of course since they were using compress() they saw it there; I bet if they removed compress() middleware, the error would have just triggered within http lib.

[dougwilson]

So just to comment, I added a test that tests the functionality, then I tried to remove the patch keeping the test, and apparently on node 0.10+ calling res.write/res.end after the socket is ignored, but it throws on node 0.8, at least in my limited testing. Something to keep a note of. Right now the removal is just sitting in it's own branch for who-knows-when.