HttpBodyStream not fired close immediate when browser is close

[bungkusansayuran]

HttpBodyStream fired close when after browser/client close and emit 1 or more data, not fired after browser/client close.

[clue]

Thanks for reporting, this actually raises an interesting issue!

Can you give some details on where you spotted this and if this is an issue for your use case?

Currently, we pause() the input stream once we no longer accept any data from the client (i.e. after the request has been processed). However, a stream that is in a paused state does not report a remote close event anymore. This means that a closed connection will only be detected once we try to send the response over the closed connection.

This refs #39 because persistent connections allow us to read the next request from the connection, thus likely keeping the connection in a resumed (un-paused) state.