broesamle/minimal-chunk

Occasional `Connection reset by peer`...why?

Opened this issue · 0 comments

Testing with curl, sometimes the connection remains intact, sometimes not:

[~]$ curl -v http://localhost:50123/
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 50123 (#0)
> GET /tenseconds HTTP/1.1
> Host: localhost:50123
> User-Agent: curl/7.47.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Sat, 10 Dec 2016 12:59:23 GMT
< Transfer-Encoding: chunked
< 
Chunk from pseudo_mondpaint: 0
Chunk from pseudo_mondpaint: 1
Chunk from pseudo_mondpaint: 2
Chunk from pseudo_mondpaint: 3
Chunk from pseudo_mondpaint: 4
Chunk from pseudo_mondpaint: 5
Chunk from pseudo_mondpaint: 6
Chunk from pseudo_mondpaint: 7
Chunk from pseudo_mondpaint: 8
Chunk from pseudo_mondpaint: 9
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer
[~]$ curl -v http://localhost:50123/
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 50123 (#0)
> GET /tenseconds HTTP/1.1
> Host: localhost:50123
> User-Agent: curl/7.47.0
> Accept: */*
> 
< HTTP/1.1 200 OK
< Date: Sat, 10 Dec 2016 12:59:27 GMT
< Transfer-Encoding: chunked
< 
Chunk from pseudo_mondpaint: 0
Chunk from pseudo_mondpaint: 1
Chunk from pseudo_mondpaint: 2
Chunk from pseudo_mondpaint: 3
Chunk from pseudo_mondpaint: 4
Chunk from pseudo_mondpaint: 5
Chunk from pseudo_mondpaint: 6
Chunk from pseudo_mondpaint: 7
Chunk from pseudo_mondpaint: 8
Chunk from pseudo_mondpaint: 9
* Connection #0 to host localhost left intact