Fix parsing responses with no CRs #96
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
sfackler
force-pushed
the
fix-no-cr-response
branch
from
0e71052 to
7370673
Compare
seanmonstar
reviewed
May 8, 2021
seanmonstar
approved these changes
May 10, 2021
Soveu
added a commit
to Soveu/httparse
that referenced
this pull request
May 11, 2021
BenxiangGe
pushed a commit
to BenxiangGe/httparse
that referenced
this pull request
Jul 26, 2021
…eanmonstar#96) Previously, parsing `HTTP/1.1 200\nfoo: bar` would incorrectly parse `200\nfoo` as a header name.
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.
The status code would previously be folded into the first header name.