Connection reset by peer with development server.
|Reported by:||Owned by:||nobody|
|Has patch:||no||Needs documentation:||no|
|Needs tests:||no||Patch needs improvement:||no|
When running the development server both with and without --nothreading, sometimes we get connection reset by peer errors. We are using Chrome and not sending any POST or GET parameters, and it works most of the time. It seems to be when there are lots of connections in a row or concurrent connections that it has issues. Clearly it should be able to handle that without resetting the connection, even if it only processes the requests serially. There's no reason it shouldn't work when running multithreaded either.
There are various other bugs in the database related to this, but they all appear to be closed or marked as duplicates of unrelated bugs and this is still an issue. See especially #18126.