Repository navigation
fix: keep IPv6 brackets in the http-to-https redirect - #272
Merged
Merged
Conversation
the redirect cut the Host at the first colon, so a request with Host [::1]:80 or [::1] was sent to https://[/path. The host now comes from discovery.HostName, the same parse route matching uses, and an IPv6 literal gets its brackets back.
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.
the http-to-https redirect cut the Host at the first colon, so a request with Host
[::1]:80or[::1]was redirected tohttps://[/path. The host now comes fromdiscovery.HostName, the same parse route matching uses since #271, and an IPv6 literal gets its brackets back:https://[::1]/path. Other hosts redirect as before.Reproduced on a static-ssl build before and after the change, plus a table test for the
Locationheader.