Warpgate should use subdomain if subdomain binding is enabled#1777
Merged
Eugeny merged 4 commits intowarp-tech:mainfrom Mar 18, 2026
Merged
Conversation
SteezyCougar
added a commit
to SteezyCougar/warpgate
that referenced
this pull request
Mar 23, 2026
…ech#1777) Co-authored-by: Eugene <[email protected]>
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
2 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.
This should solve #1773
The only potential item here is that this enforces you ALWAYS using the bound sub-domain if it's configured, but I think that actually makes a lot of sense. if you set a subdomain, it's logical you want to always be using that sub-domain.