HTTPS

As you might already know search engines (Google) sees www.domain.com and domain.com as two separate domain names. If you are not using 301 redirects (www to non-www or vice verse)you might get penalized for duplicate content.  In Ngnix, there is a simple solution how to make such redirect happen, see: Ngnix Redirect To WWW Now, things get a bit complicated when https versions are involved. See: Linode: How To Secure Nginx with Let's Encrypt on Ubuntu 12.04 Once your website has https…

Today I noticed that SSL connection on this blog had errors due to “mixed content”, meaning HTTPS site was loading additional content that was served over insecure HTTP. After a little bit of digging in the console, I discovered that the issue was due to our Disqus comment plugin loading over HTTP. I felt surprised learning that Disqus is serving HTTP content, and quickly googled, are there other webmasters complaining about this, and I found a few articles. What felt even more surprising was…

Recently I made a switch from http to https. I was pretty pleased with results, and started to wait for possible SEO boost from Google. As time passed, instead of boost some traffic drop started to appear in my Google Analytics account. I cannot say for sure is this because of https thing or some major update in Google Search algorithm (Penguins & Pandas) , I just wanted make sure everything works right on my site. Traffic dropped to 0 (hourly view) Most probably it is just some glitch…

It was about a month ago - when I successfully installed secure https pages for my blog, I opted for using free certificate provided by Let's Encrypt certificate authority. I first heard Let's Encrypt certificate authority from KeyCDN. It was super easy and fast to create SSL certificates for my Linode powered Nginx box. Unfortunately - just a few days later I noticed a deadly screen - Your connection is not private Your connection is not private Google Chrome screen I was using Windows XP…