Setting Up Reverse Proxy Delivery for a Routing Flow

Confirm both destination URLs, TLS availability, expected Host header, authentication assumptions, asset paths, redirects, cookies, and geographic reachability. Test each upstream directly before placing the router between it and the browser.

Determine whether the upstream expects its own hostname or the public campaign host. This choice can affect virtual hosting, absolute URLs, cookies, redirects, and application-generated canonical links, so verify behavior rather than relying on a default.

Choose a proxy timeout that reflects the upstream and campaign experience. Decide which safe response should appear when DNS, TLS, connection, or response timing fails; an indefinite wait is not a useful fallback.

Load HTML, scripts, styles, images, forms, navigation, and redirects through the public host. Look for mixed content, upstream host leakage, broken relative assets, incorrect cookie scope, and redirect loops.

Compare a known request at the upstream and public flow, inspect the routing event, and test both destinations plus failure handling. Retain the previous delivery configuration so rollback is fast if upstream behavior changes.