http: delay input stream close until responses sent #1391
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
Previously, https:// servers would fail to send a response whenever a client sent a "Connection: Close" HTTP/1.1 response. This was hidden mostly by the case-sensitive parse of "Close", where typical clients send "close". Commit c14f931 fized the parsing to be case insensitive, which makes the underlying issue manifest. Previously we were mostly ignoring `Connection` headers.
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.
This is a workaround for issue #906 when using TLS connections to an httpd service.
Previously, https:// servers would fail to send a response whenever a client sent a "Connection: Close" HTTP/1.1 response.
This was hidden mostly by the case-sensitive parse of "Close", where typical clients send "close". Commit c14f931 fized the parsing to be case insensitive, which makes the underlying issue manifest. Previously we were mostly ignoring
Connectionheaders.