HTTP overlay home button redirects to bind domain instead of external_hosts.http #2005
Unanswered
Luxeon-dev
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Warpgate version: 0.23.4
Setup:
Warpgate behind a reverse proxy
HTTP target with a bind domain configured (
target.warpgate.example.com)external_hostinwarpgate.yamlset towarpgate.example.comObserved behavior:
When accessing a target via its bind domain (
target.warpgate.example.com) and clicking the "home" button in the injected session overlay, the browser is redirected totarget.warpgate.example.com/@warpgateinstead ofwarpgate.example.com/@warpgate.Inspecting the
/api/infoendpoint while on the target domain confirms thatexternal_hostreturns the bind domain value of the active target, whileexternal_hosts.httpcorrectly returnswarpgate.example.com.Expected behavior:
The home button should redirect to
warpgate.example.com/@warpgate(the main Warpgate host), regardless of the active target's bind domain.Question:
Is this intentional? If the bind domain is meant to fully isolate the target, is there a recommended way to configure the home button to point back to the main Warpgate host?
Beta Was this translation helpful? Give feedback.
All reactions