Redirects
View as MarkdownRedirect one hostname to another at the edge.
A domain attached to your project can either serve your application directly or redirect to another hostname. Redirects happen at Atlasflow's edge, before traffic reaches your container.
When to use a redirect
The most common use is consolidating www and apex domains so users always land on one canonical hostname, for example redirecting www.example.com to example.com.
Configure a redirect
- Add the domain you want to redirect (for example
www.example.com) and verify it. See Custom domains. - In the domain settings, set it to redirect to a target hostname.
- Choose a redirect status code.
Supported status codes
| Code | Meaning | Use when |
|---|---|---|
| 301 | Moved Permanently | The redirect is permanent and should be cached. |
| 302 | Found | A temporary redirect. |
| 307 | Temporary Redirect | Temporary, preserving the request method. |
| 308 | Permanent Redirect | Permanent, preserving the request method. |
For canonical domain consolidation, 301 or 308 is usually the right choice.
How it works
A redirecting domain doesn't route to your container at all. Atlasflow responds at the edge with the chosen status code and the target location, so your application never sees the request.
Next steps
- Custom domains: add and verify the domain first.
- DNS configuration: the records the redirect domain needs.