Edge rulesRedirects, rewrites and header rules, without touching your server.
Rules run at the edge, before a request reaches your origin. Redirect old URLs, rewrite paths, add or remove headers, block what you never serve and show your own error pages, all from one list.
Shape the request
Redirect rules move visitors to a new URL. Rewrite rules change the path your server sees while the visitor's address stays the same. Header rules add, change or remove request and response headers.
- Redirect rules
- URL rewrites
- Request and response header rules
Refuse what you do not want
Block by country, path or hostname, put Basic Auth in front of a private path, and switch on security headers and HSTS per domain. A header your origin already sends wins for no-sniff and referrer policy.
- Country, path and host blocking
- Basic Auth for private paths
- Security headers and HSTS
Order, scope and a dry run
Rules run in order, so priority is yours to set. Scope a rule to all hostnames or to chosen ones, and save it in dry run to see what it would have done before it does it.
- Priority you control
- Host and path scoping
- Dry run and custom error pages
Frequently asked questions
What is the difference between a redirect and a rewrite?
A redirect sends the visitor's browser to a different URL. A rewrite changes the path your server receives, and the address in the browser does not change.
Can I test a rule safely?
Yes. Save it in dry run. It logs each match as if it had acted and lets every request through.
Can rules apply to only one subdomain?
Yes. A rule can cover every hostname of the domain or only the ones you select.
Does the order of rules matter?
Yes. Rules run in order, so put allow-style rules above block-style ones.