David Strawn
David Strawn
@armanbilge @kyri-petrou I can reproduce with `ab` using the `-k` flag, but when I remove it I'm no longer able to reproduce it. I think this might be related to...
If I set the socket timeout in ember to a low value, the app resumes after the connection is closed. I'm not entirely sure what that means yet...
Another couple notes, according to the packets I'm seeing on the wire, `ab` is sending HTTP 1.**0** request. ``` GET / HTTP/1.0\r\n Connection: Keep-Alive\r\n Host: localhost:8080\r\n User-Agent: ApacheBench/2.3\r\n Accept: */*\r\n...
@kyri-petrou just to narrow down the scope here, have you experienced this with clients other than `ab`?
@kyri-petrou @armanbilge I believe I've found the cause of the issue. This actually is not related to any of the middlewares or even http4s, it's an issue with `ab`. Here...
@armanbilge yeah, we can make this better on 1.x, but if we can't generally fix all edge cases for an http 1.0 client.
@armanbilge do we claim to have any http 1.0 support? I thought we just didn't support it.
@kyri-petrou take those timings with a huge grain of salt. I was running that on my dual core laptop from 2015 while concurrently building the linux kernel. So....the system was...
@rossabaker thanks for all that context. I didn't realize that HTTP/1.1 had provisions for talking to an HTTP/1.0 client, although that does makes sense.
@zarthross thoughts on merging this?