feat: support custom gateway with x-dstack-target-gateway header#25
Open
feat: support custom gateway with x-dstack-target-gateway header#25
Conversation
This adds support for routing to target services using the x-dstack-target-host header as an alternative to x-dstack-target-* headers. Changes: - Add target_host field to DstackRequest, read from x-dstack-target-host header - Update proxy_request to support three routing priorities: 1. x-dstack-target-app/port/instance headers (highest priority) 2. x-dstack-target-host header (if it matches target service pattern) 3. Delegate to dstack.sock (fallback) - Preserve Host header behavior from main branch (passed through as normal header) - Integrate with x-dstack-target-gateway feature from feature-target-gateway branch
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
1 participant
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.
No description provided.