Fix connection close bug when response write over 5 seconds #294
Conversation
This file contains hidden or 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
…g asynchronous write response data
rustyx
added a commit
to rustyx/crow
that referenced
this pull request
Feb 8, 2019
GerHobbelt
pushed a commit
to GerHobbelt/crow
that referenced
this pull request
Dec 17, 2021
upgraded parser from 2.3.0 to 2.9.4
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix connection close in tick time(5 seconds default) even if remaining to write response data.
When writing response to client over 5 seconds, connection will close by timer. so if big response data or weak network condition make reset connection before received all response.