http res.on('end') not working

Thanks - annoyingly end doesn't even have its own heading as an event in the node http reference, I guess since it's on the underlying stream.

It's odd that close doesn't work in node though. the reference sort of implies it's like end and should work - but perhaps the underlying socket is kept open and so close doesn't get called until a while later.

I'll add an end event as well though - it should be in the next release, but I added an issue for it so you can keep track of it here