Routing
Redirects & Headers
Rewrite where requests go and control the response headers your site sends — both applied at the edge by the Deploxa proxy, with no rebuild required.
Redirects
In the dashboardProject → Redirects
A redirect maps a source path to a destination. Mark it permanent for a 308 (cached by browsers); leave it temporary for a 307.
| Source | Destination | Permanent |
|---|---|---|
/old-pricing | /pricing | Yes (308) |
/docs | https://example.com/docs | No (307) |
Redirects take effect immediately when you save — there's no deployment involved.
Custom headers
In the dashboardProject → Headers
Add response headers to matching paths — useful for security headers, caching policy, or CORS. A rule has a source pattern (defaults to all paths), a header name, and a value.
text
Source: /(.*) Name: Strict-Transport-Security Value: max-age=63072000; includeSubDomains; preload Source: /assets/(.*) Name: Cache-Control Value: public, max-age=31536000, immutable
Matching & precedence
The source is a path pattern (the default /(.*) matches everything). Redirects are evaluated before your app sees the request, so a matching redirect short-circuits routing. Header rules are additive — every enabled rule whose source matches contributes its header to the response.