fix: cancel accept if client disconnected #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for the PR! Could you please add a test that exercises this scenario? |
|
@bartlomieju A test was added. |
|
Thanks, I think I will need to land #29 first before we merge this PR. |
|
@wille-io could you rebase this? |
|
omw |
wille-io
force-pushed
the
cancel-accept-on-client-disconnect
branch
from
d46f1bb
to
6de75ec
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If a client disconnects while inside the accept loop, the socket will read 0 bytes indefinitely, resulting in a DoS.
This fix returns from the
acceptfunction with aConnectionReseterror.