-
Notifications
You must be signed in to change notification settings - Fork 184
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Parse headers with no whitespaces (#856)
Motivation: The whitespace between the `:` and a header value is optional [1] but we consider it as required [2] hence skip a character after the `:`. As the result, header value may miss the first character. [1] https://tools.ietf.org/html/rfc7230#section-3.2 [2] `header-field = field-name ":" OWS field-value OWS` Modifications: - Do not skip a character after `:`; - Add more tests for headers with no whitespace and for mixed whitespaces; Result: Headers parser does not skip the first value character when there is no whitespace after `:`.
- Loading branch information
1 parent
1364258
commit e3528e6
Showing
3 changed files
with
89 additions
and
3 deletions.
There are no files selected for viewing
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
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
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