[Proxy configuration] Add help for hidden SSL termination #19422
Conversation
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
javiereguiluz
added a commit
that referenced
this pull request
Jan 16, 2024
This PR was submitted for the 7.1 branch but it was merged into the 6.3 branch instead. Discussion ---------- [Routing] [url generation] note on forcing https this got me confused when trying to ignore the problem i had in #19422 - i think cross-linking the proxy configuration here is helpful for people who also try to skirt doing a correct setup in their infrastructure. Commits ------- dc2fbdb note on forcing https
javiereguiluz
force-pushed
the
patch-3
branch
from
ad1195e to
96634f5
Compare
|
David, thanks for this other contribution too. |
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.
i struggled quite a bit trying to make links generated with https in azure.
the ssl termination is done by azure, but they "hide" that it happens, there is no information in the HTTP headers about the proxy that does it.