Latest news, food, business, travel, sport, Tips and Tricks...

Turn on HTTPS on Our Blogspot Blog

HTTPS is key to web security; it protects the integrity and confidentiality of information sent between websites and visitors' browsers. If you wish visitors to access your blog over HTTPS, you can activate HTTPS and HTTPS redirect.

There are three main benefits to using hypertext transfer protocolS rather than HTTP to access your blog:

  • It helps make sure your visitors open the right website} and aren’t being redirected to a malicious site.
  • It helps discover if an attacker tries to alter any information sent from Blogger to the visitor.
  • It adds security measures that create it more durable for others to listen to your visitors’ conversations, track their activities, or steal their data.

To turn on HTTPS for your custom domain blog:

Turn on HTTPS on Our Blogspot Blog

Sign in to Blogger.

  1. In the top left, click the Down arrow Down Arrow.
  2. Select the blog to update.
  3. In the left menu, click Settings then Basic.
  4. On the proper, below "HTTPS" and "HTTPS availability," choose yes.
  5. Even if we did not previously turn on this setting, our blogs will have an HTTPS version enabled.

There is setting called HTTPS Redirect that allow to opt-in to redirect HTTP requests to HTTPS. While all blogspot blogs will have an HTTPS version enabled, if we turn on this new setting, all visitors will be redirected to the HTTPS version of our blog at https://<your-blog> even if they go to http://<your-blog> If you choose to turn off this setting, visitors will have two options for viewing your blog: the unencrypted version at http://<your-blog> or the encrypted version at https://<your-blog>

If we turn on this option, please be aware about mixed content. It may cause some of our blog's functionality not to work in the HTTPS version. Mixed content is often caused by typed url in HTTP protocol e.g http://<your-blog>, etc. If we have that, mixed content warning alerts will shown, that is the sign we must fix it by changing its protocol to HTTPS.