Got a website?
Secured with HTTPS and an SSL certificate?
You’d know if someone tried to register their own certificate for your domain and masquerade as you, right?
If you answered Yes, Yes and No, and you’re using Cloudflare, you can fix that at the flick of a switch (well, click of a button!).
Read on to find out how…
In my last post, Grav in Azure part 4 - Adding DNS and Cloudflare to an App Service Web App, I demonstrated how to configure your Azure web app and its DNS to be managed by Cloudflare.
In this post, we’ll go ahead and take a look at and optimise our Cloudflare configuration for performance and security.
In my last post, Grav in Azure part 3 - Creating an Azure Web App with code deployed from Git, I demonstrated how to setup a webapp in Azure and deploy code to it from a Bitbucket repo with the Grav Blog Site skeleton code.
In this post, we’ll take a domain name and pass the management of the DNS to Cloudflare then link the domain name to the Azure origin address and url so we can take advantage of Cloudflare features (the subject of a future post in this series).
In this post, I discuss my requirements for my blog, what I’ve chosen to build it with and why.