Skip to content

http: emit ERR_STREAM_DESTROYED if the socket is destroyed

Rodrigo Muino Tomonari requested to merge github/fork/mcollina/http-outgoing-destroyed into master

The pipeline utility assumes that a stream is going to error if it could not be written to it. If an http.OutgoingMessage was piped after the underlining socket had been destroyed, the whole pipeline would not be teared down, resulting in a file descriptor and memory leak.

Checklist
  • make -j4 test (UNIX), or vcbuild test (Windows) passes
  • tests and/or benchmarks are included
  • commit message follows commit guidelines

Merge request reports