RDTKF-25112 Clarify --proxy scope and document relay-server pattern - #204
Open
rmlos wants to merge 2 commits into
Open
RDTKF-25112 Clarify --proxy scope and document relay-server pattern#204rmlos wants to merge 2 commits into
rmlos wants to merge 2 commits into
Conversation
--proxy only covers the Cloud Connector to Private Gateway connection; the connection to each remote-host is always dialed directly. Also documents that outsystemscc is a raw TCP/UDP passthrough (no Host header or SNI rewriting) and that a relay server is the supported way to terminate TLS or present a different hostname to the destination.
Moves the raw-passthrough/relay-server explanation from Usage into Overview, where it belongs conceptually, and trims it to the new information it adds over the existing TLS/CA note already in Usage. Rewrites negated statements as positive ones per MSSG/GDSG guidance.
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.
Summary
--proxyonly applies to the connection from Cloud Connector to the Private Gateway (<server>). The connection to each<remote-host>is always dialed directly by the host's local network stack, and never passes through--proxy.outsystemsccis a raw TCP/UDP passthrough: it doesn't rewrite the HTTPHostheader or the TLS SNI. Adds guidance to use a relay server as<remote-host>when the real destination needs TLS terminated with a public-CA certificate or expects a different hostname/SNI than the connecting app presents.Raised from a customer question in Slack, tracked in RDTKF-25112.