Server closes connection on chunked pipelining

[ronag]

This was a bit surprising for me. It seem the server always ends the connection at the end of a request which sent a chunked body, i.e. this will always close the connection once the first request has completed.

@mcollina Are you familiar with this behavior?

test('pipelined POST does not interleave', (t) => {
  t.plan(5)

  const server = createServer((req, res) => {
    req.on('data', chunk => {
      console.error(chunk)
    }).on('end', () => {
      res.end()
    })
  })
  t.tearDown(server.close.bind(server))

  server.listen(0, () => {
    const client = new Client(`http://localhost:${server.address().port}`, {
      pipelining: 2
    })

    let a = 0
    client.request({
      path: '/',
      method: 'POST',
      body: new Readable({
        read () {
          this.push(a++ > 128 ? null : 'a')
        }
      })
    }, (err, data) => {
      console.error('a', err)
    })

    let b = 0
    client.request({
      path: '/',
      method: 'POST',
      body: new Readable({
        read () {
          this.push(b++ > 128 ? null : 'b')
        }
      })
    }, (err, data) => {
      console.error('b', err)
      // t.ok(err)
    })
  })
})

[ronag]

Moved to PR #76