feat: not returning UnexpectedEof when client drop without close_notify #743
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
dswij
changed the title
Noah-Kennedy
approved these changes
Jan 19, 2024
seanmonstar
approved these changes
Jan 19, 2024
|
🙌🏻 💚 |
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.
closes hyperium/hyper#3427
This PR makes it so that if we encountered
UnexpectedEofas a server, and when there is nothing else to send (i.e. we sent what the client wanted),Connection::pollwill not return anErr.Note that this does not change the client behaviour when the server closed the connection abruptly.
Something to consider is whether we should handle this in hyper instead. But I don't see a good reason why we shouldn't put it in
h2