Watson Lite: Fix Headers Not Being Parsed Correctly #156
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
|
@dotnet-policy-service agree company="SamsidParty" |
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.
Info
This fix to the watson lite header parsing code allows for header values to contain colons.
Previously, headers values would be ignored if they had colons in them.
This will help with parsing certain headers and will make it more in line with the HTTP/1.1 spec.
Motivation
Browsers usually sent a
Hostheader to the server, which sometimes includes a colon to delimit the port number:Host: 127.0.0.1:8080. Without this fix, theHostheader is ignored. With this fix, the header is parsed correctly.