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
- Open Topology → Routes.
- Bind host + cluster.
- Set path and method matchers.
- Save.
Steps — transforms
- Open Advanced → Gateway (transforms / traffic policies) or route transform UI.
- Add header set/remove, path rewrite, or redirect rules.
- 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.