Delivery
Routing configuration
Routing configuration covers everything between a visitor's request and your origin server: where it's sent, how it's rewritten, and what gets served without touching the origin at all.
How it works
- Origins define where traffic is proxied to, with redirect and rewrite rules layered on top
- Static file overrides let you serve specific paths (like a maintenance page) without an origin round-trip
- Every configuration change is recorded in a history log with enough context to see what changed and why
Good to know
- Origins are re-validated by the same safety guard used for audits, so internal or non-public addresses are rejected
- History entries are what make rollback decisions possible after an unexpected change