EdgeRules™ Now Included in All Accounts
We’re excited to announce a new feature, EdgeRules™, giving you instant control over static content delivery. Originally developed as a premium feature of MaxCDN, EdgeRules is now available in all SecureCDN accounts for no additional charge.
With EdgeRules you can modify the way content gets fetched from your origin, customize asset delivery, security measures, SEO, and mobile experience. EdgeRules also lets you reduce the number of calls made to your origin server when you block requests, create custom redirects, manipulate headers, and more.
Getting Started (with EdgeRules)
- Log in to your Dashboard. (If you don’t have an account, get one.)
- Click on Sites in the left navigation bar.
- Choose a Site and click Manage.
- On the Summary page, click on CDN to open the dropdown menu.
- Select EdgeRules and you’re in!
Naturally, you can create your own rules from scratch. But to give you an idea of what you can use EdgeRules to do (and a headstart), we’ve created these rule recipes:
|CORS Headers||Redirect All Bots||Add Canonical Header|
|Hide X-Powered-By Header||Redirect by Referrer||Add X-Robots-Tag|
|Hide Server Header||Redirect by User-Agent|
|Hide S3 Headers||Redirect by Country|
|Force HTTPS Connections|
|Add X-XSS-Protection Header|
|Add X-Frame-Options Header|
|Block by Country|
When you’re ready to create a rule, open a recipe and click CREATE RULE FROM RECIPE. Customize the recipe to your taste, and then click to enable the rule right away, or save it to finish later. You can read more about these individual and custom recipes on our EdgeRules page.
All Your Content, Covered
You might be thinking, “EdgeRules sound great for static content, but what about my dynamic content?” Don’t forget that every StackPath SecureCDN account also has our web application firewall (WAF) included. WAF and EdgeRules operate independently but together cover delivery of all your content. Firewall Rules and Policies primarily protect the origin of your dynamic content (and also still apply when static content is grabbed from your origin), while your EdgeRules give you more granular control over accessing the origin of your static content.