Fix: Handle client connection reset for keep-alive connections #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #86
TCPSocket#eof?will raiseErrno::ECONNRESETif the connection has been reset. This is currently not handled properly inWEBrick::HTTPServer#run. This was reported by @carlhoerberg, but incorrectly addressed in #86.Preconditions to hit this issue:
Connection: keep-aliveThis will leave the server believe that the connection is still good and fail in
WEBrick::HTTPServer#runwhen testingTCPSocket#eof?in the next iteration of#run.The fix is to rescue
Errno::ECONNRESETwhen checking for#eof?.Testing this is a little tricky, here is how I approached it:
WEBrick::HTTPServer/Connection: keep-aliveTCPSocketobject out of theNet::HTTPinstance and configure it to linger on close and forcefully reset the connection, dropping all remaining data. This will send aRSTto the serverTestWEBrickshutting down, before we hit the issue, we need to wait a little bit