Uh oh!
There was an error while loading. Please reload this page.
Validate Host header for HTTP/1.1 requests as per RFC - #127
Merged
Conversation
clueforce-pushed
the
error-invalid-host
branch
from
February 19, 2017 15:17
69dc47c to
16b425bCompareclue
commented
Feb 19, 2017
MemberAuthor
Rebased now that #125 is in |
jsor
approved these changes
Feb 19, 2017
WyriHaximus
approved these changes
Feb 20, 2017
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
HTTP/1.1 requests MUST include a valid host header (host and optional port) as per RFC: https://tools.ietf.org/html/rfc7230#section-5.4
Builds on top of #124
Refs #125