address three bugs in forwarded header parsing#375
Merged
Fishrock123 merged 1 commit intohttp-rs:mainfrom Aug 5, 2021
Merged
Conversation
b792450 to
4d65eaf
Compare
Fishrock123
approved these changes
Jul 30, 2021
Member
Fishrock123
left a comment
There was a problem hiding this comment.
Would be nice to backport
Member
Author
|
do we have a branch or tag for 2.x? |
Fishrock123
added a commit
that referenced
this pull request
Aug 10, 2021
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
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.
Previously,
forsection to be first (Error in parser for the "Forwarded" header #374)starts_with_ignore_casewould panic (only used in forwarded currently)pub(crate)) token did not successfully parse 1-character tokens due to an off-by-one errorThis can be fairly easily backported to the 2.x line if there's interest
closes #374