{"id":1909,"date":"2018-03-13T00:00:17","date_gmt":"2018-03-13T00:00:17","guid":{"rendered":"https:\/\/atozcrypto.org\/?p=1909"},"modified":"2018-03-13T00:04:16","modified_gmt":"2018-03-13T00:04:16","slug":"http-vs-https-whats-the-difference-and-why-should-you-care","status":"publish","type":"post","link":"https:\/\/atozcrypto.org\/http-vs-https-whats-the-difference-and-why-should-you-care\/","title":{"rendered":"HTTP vs. HTTPS: What’s the Difference and Why Should You Care?"},"content":{"rendered":"
<\/a><\/p>\n You may have heard people urging you to switch your website to the HTTPS security encryption.\u00a0They cite Google\u2019s announcement that\u00a0HTTPS is a ranking signal<\/a>\u00a0and that failure to switch could mean your ranking will take a hit.<\/p>\n And that would mean less traffic and less business.<\/p>\n But, can a product that costs around $100 per year really make that much of a difference?\u00a0And if so, how straightforward is it to make the switch?<\/p>\n Let\u2019s face it, until recently, HTTPS was really used only by ecommerce sites for their payment pages.\u00a0Things can get confusing, and the question many business owners face is whether or not the hassle of switching to HTTPS is worth it.<\/p>\n So,\u00a0let\u2019s look at the arguments for and against.\u00a0But first of all, what exactly is HTTPS?<\/p>\n HTTP stands for\u00a0hypertext transfer protocol<\/a>. It\u2019s a protocol that allows communication between different systems. Most commonly, it is used for transferring data from a web server to a browser to view web pages.<\/p>\n <\/a>The problem is that HTTP (note: no “s” on the end)\u00a0data is not encrypted, and it\u00a0can be intercepted by third parties to gather data being passed between the two systems.<\/p>\n This can be addressed by using a secure version called HTTPS, where the “S”\u00a0stands for secure.<\/p>\n This involves the use of an\u00a0SSL certificate<\/a>\u00a0— “SSL” stands for\u00a0secure sockets layer —\u00a0which creates a secure encrypted connection between the web server and the web browser.<\/p>\n Without HTTPS, any data passed is insecure. This is especially important for sites\u00a0where sensitive data is passed across the connection, such as ecommerce sites that accept online card payments, or login areas that require users to enter their credentials.<\/p>\n If you are familiar with the backend of a website, then switching to HTTPS is fairly straightforward in practice. The basic steps are as follows.<\/a><\/p>\n In terms of the setup of the SSL certificate — points one and two above —\u00a0this is fairly straightforward, and your hosting company will be able to assist you.<\/p>\n Also\u00a0bear in mind that for a small website this will be fairly straightforward, as some of the above points won\u2019t apply in scenarios\u00a0such as code libraries and\u00a0CDNs.\u00a0However, for a larger site, this is hardly a non-trivial event and should be managed by an experienced webmaster.<\/p>\n Source:\u00a0entrepreneur.com<\/p>\nWhat is HTTPS, and why do you need it?<\/h2>\n
What\u2019s the process for switching to HTTPS?<\/h2>\n
\n