Serving Github Pages via HTTPS with CloudFlare permalink

I had to do some exploration into CDN and site optimization options as part of a “Buy vs. Build” analysis. One option stood out above the rest in CloudFlare. I took the opportunity to use this site to not only evaluate the performance boost, but also finally serve the site over HTTPS.

This site is a perfect candidate to evaluate baseline performance since it is a pure static site. With added dynamicism through custom pages rendered server side adds a bit of complexity, but the numbers track similarly.

CDN and site optimizers like CloudFlare employ regionally located servers cache your static content closer to your users, thereby reducing the number of hops, thereby reducing the load times for your site. It also provides for lighter load on your servers, and decreased bandwidth.

CloudFlare's regional map of servers

They're services also include traffic analysis to mitigate DDOS attacks, prevent (basic) SQL injection attacks, and give another source for analytics into site access patterns by everything from users to site crawlers.

I like that CloudFlare serves as an in-line cache. At previous employers, we had utilized a really messed up implementation of the Akamai services that required copying a bulk of our static content to a separate server that the CDN would poll for updates. It made the deployment and maintenance much more of a headache. However, with CloudFlare, setup was a breeze (see directions below).

CloudFlare in-line optimization

Set up HTTPS for gh-pages on CloudFlare

  1. Sign up for a free CloudFlare account.

  2. Make sure that all the records in your existing Zone file are copied over…

  3. Update the DNS Nameservers in your domain registrar to point to those at CloudFlare…

    Old nameservers, meet new nameservers

  4. Change SSL settings from Full to Flexible


  5. Setup Page Rule to match all urls to force HTTPS…

    URL Pattern:*

    Always use https: On

    CloudFlare Page Rule

  6. Update your jekyll configuration to include https in the site url property and enable the enforce_ssl property…

    url: ""
  7. Make sure the canonical link in your DOM head

        <link rel="canonical" href="">
  8. Revel in your new found security


Performance Comparison

I was all setup to run some actual performance tests this evening from home and post the numbers, but I came home to wildly varying internet speeds:

Go, Comcast! Go!

I'll post numbers soon.

Update (2016/01/12)

My world is right!

Much better!





Viewing just this post serves only three things from Github Pages:

All-in-all, I think it was worth the time learning more about CloudFlare and other edge service providers. Hopefully you will enjoy the new and improved website!

© 2020