Expedited WAF on Heroku requires that a site return a 200 HTTP status code before setup can begin.
Why? This helps with troubleshooting and setup by making sure that new sites are configured and functional prior to implementing the WAF.
If you're launching a new site though you may wish to set up the WAF prior to launch.
A Heroku application that:
- Has not yet had any code deployed to it
- Has DNS/Domains setup correctly
Will return a 502 HTTP Status Code along with this page:
The quickest fix is to set up a static "coming soon" page that while functionally not different than the "Heroku | Welcome to your new app!" page will instead return a 200 HTTP Status code and let you proceed with WAF setup.
This repo is exactly that and the deployed page will look like screenshot below:
Add this to your Heroku app by clicking on the Heroku deploy button below.
- Deploy this static site + coming soon page into your Heroku app.
- The app will then return a 200 HTTP status code
- You can then proceed with WAF setup.
Please email support@expeditedsecurity.com if you need help getting this setup.