middleware: handle Host routing via Request.Host#1120
Open
happysnaker wants to merge 1 commit into
Open
Conversation
Signed-off-by: happysnaker <73147033+happysnaker@users.noreply.github.com>
Contributor
Author
|
Maintainer note: this patch intentionally targets the existing documented |
Contributor
Author
|
Keeping this warm: the intent of this patch is still to make the documented |
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.
Summary
Request.HostforRouteHeadersrules targetingHostnet/httphost promotion behavior in the middleware docsWhy
net/httppromotes the HTTP Host header toRequest.Hostand removes it fromRequest.Header, so the existing Host-based example inRouteHeadersis misleading for normal browser traffic. This patch makes Host routing behave the way users expect and updates the docs/tests accordingly.Closes #691
Note
This PR supersedes #1118, which I had to close after the original fork relationship was broken during repo visibility changes on my side. The code/content is the same contribution path, now resubmitted from a proper public fork.