Migration to HTTPS

  We have finally migrated from HTTP to HTTPS. As you can see, there is a green lock icon in the address bar and the url of this page begins with https instead of the usual http. This article describes why and how Windows Code Bits underwent the process of migration to HTTPS. We’ll also tell you how you can migrate your website to HTTPS if you want to.

Migration to HTTPS

Migration to HTTPS

Migration to HTTPS

  As you know, internet has become a vital part of our daily life. Nowadays, most of our daily tasks involve the use of the web on various types of devices ranging from computers to tablets to smartphones. However, this also raises a serious risk. Our data has to be transmitted from one place to another constantly and if appropriate security measures aren’t used, unscrupulous persons may access and manipulate our data.

  Now, HTTP works without any kind of encryption and therefore, any data transmitted over HTTP is prone to interception by malicious persons. This is where HTTPS comes in. As you probably know, HTTPS stands for HTTP Secure (also known as HTTP over SSL/TLS). HTTPS ensures that the data transferred between two computers is encrypted and hence cannot be intercepted.

  Usually, blogs (like this one) don’t need encryption since they don’t handle any ‘sensitive’ user data e.g. Credit Card data. However, we want to ensure that our visitors can access this website without the fear that their activities could be intercepted by a third party. We believe that every communication over the web should be secure and HTTPS helps us do exactly that. Most other blogs, even the most prominent ones, do not use encryption. This is very bad from the perspective of security because those blogs accept user email addresses and other data (either for blog comments, or email list, or contact form) without ensuring that the transmission of that data is private and secure. In our opinion, all of them should perform the migration to HTTPS as soon as possible. If you have a website of any kind, we strongly recommend that you start using HTTPS if you aren’t doing so currently.

The process of migration to HTTPS

  The process of migration was fairly simple, though it must be admitted that some of things involved in the process took a fair bit of time. We contacted our hosting provider (A2Hosting) and told them that we needed HTTPS on our website. We also told them that we wanted to use the Let’s Encrypt SSL certificate (which is completely FREE). That’s it! They enabled Let’s Encrypt on Windows Code Bits and now it is using HTTPS.

Please Note that other SSL certificates require yearly payments of $49 or more (depending upon the certificate provider).

  On our side, we still had some work to do. We had to change WordPress settings to use HTTPS in all permalinks. We also modified all the links inside our posts to ensure that they use HTTPS version of urls. As you can see, our website is now fully encrypted.

  So, if you want to get HTTPS on your website and have no clue where to begin, contact your hosting provider. If you’re familiar with this stuff, you should have no problem doing it all yourself. If you liked this article, SHARE IT…!!!

One comment

  • It’s a very informative post for me as I am always looking for new content that can help me and my knowledge grow better.

Leave a Reply

Your email address will not be published. Required fields are marked *