ShieldGate Docs

Topology

Routes and transforms

Match traffic and reshape requests before upstream.

Goal

Connect hosts to clusters with routes, and apply transforms when the upstream expects different paths or headers.

Prerequisites

  • Host and cluster exist.
  • Permissions proxy.routes.* and gateway transform permissions as needed.

Steps — routes

  1. Open Topology → Routes.
  2. Bind host + cluster.
  3. Set path and method matchers.
  4. Save.

Steps — transforms

  1. Open Advanced → Gateway (transforms / traffic policies) or route transform UI.
  2. Add header set/remove, path rewrite, or redirect rules.
  3. Save and confirm publish.

Transforms are distributed in the tenant snapshot and applied by YARP on the data plane.

Verify

  • Request matches the route (correct upstream).
  • Transformed headers/paths appear on the upstream (log or echo service).

Tips

  • Prefer explicit path prefixes over accidental catch-alls in multi-app tenants.
  • Keep redirects in transforms when you want edge-level HTTP→HTTPS or path moves.