diff options
| author | Zhiming Wang <zmwangx@gmail.com> | 2016-09-01 21:44:35 +0800 |
|---|---|---|
| committer | Zhiming Wang <zmwangx@gmail.com> | 2016-09-01 21:44:35 +0800 |
| commit | ab39a77b0eb4ce3e8fa219ea76fb9616a8aa7758 (patch) | |
| tree | d4427686865fe00ccafc2a205e9fcc2826bb55ee /source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md | |
| parent | 0eb83ba69519d6693281e441da1e7a0408a231d3 (diff) | |
| download | my_new_personal_website-ab39a77b0eb4ce3e8fa219ea76fb9616a8aa7758.tar.xz my_new_personal_website-ab39a77b0eb4ce3e8fa219ea76fb9616a8aa7758.zip | |
20160901 This blog is now behind CloudFlare
Diffstat (limited to '')
| -rw-r--r-- | source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md b/source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md new file mode 100644 index 00000000..e471ec8e --- /dev/null +++ b/source/blog/2016-09-01-this-blog-is-now-behind-cloudflare.md @@ -0,0 +1,17 @@ +--- +title: "This blog is now behind CloudFlare" +date: 2016-09-01T20:11:00+08:00 +date_display: September 1, 2016 +--- + +Back in July I registered the domain [zhimingwang.org](http://zhimingwang.org) and pointed this GitHub Pages-powered blog at it. Since then I have lost the HTTPS badge due to GitHub Pages not supporting HTTPS on custom domains (see [isaacs/github#156](https://github.com/isaacs/github/issues/156)). + +There have been a lot of discussions on isaacs/github#156 (and stupid [+1's](/blog/2016-01-18-me-too-comments-on-github.html) too). Among the proposed solutions is putting the website behind CloudFlare. I carefully investigated [this option](https://blog.cloudflare.com/secure-and-fast-github-pages-with-cloudflare/) and read almost all the arguments against it. I fully understand CloudFlare's SSL models (summarized in the image below), and I do realize most if not all of the limitations of CloudFlare, including CloudFlare being a huge MITM (which is inevitable for a CDN anyway), as well as most if not all of its annoyances, including CAPTCHAs which I myself would occasionally run into when I'm browsing with PIA VPN, and JavaScript-based browser checks. + +.](/img/20160901-cloudflare-ssl-modes.png) + +After careful evaluation, I decided that CloudFlare's SSL model is good enough for me. After all, this is just a damn blog, with nothing sensitive. TLS is still nice because it guards against prying eyes and unethical ad-injecting ISPs or Wi-Fi hotspots, but other than that, it isn't necessary. + +End result: this blog is now behind CloudFlare. Readers should now see that green HTTPS badge again (note that I'm enforcing HTTPS — without HSTS though). As for CAPTCHAs, I have adjusted the firewall settings on CloudFlare's dashboard — "Security Level" to "Essentially Off" and "Challenge Passage" to 1 year, so hopefully it won't be too annoying.[^tor] + +[^tor]: I don't use Tor, and don't intend to raise Big Brother's suspicion by using it, so I have no idea of the actual Tor experience. |