HTTP vs HTTPS: What difference does it make to security?
We look at the difference between the two and tell you how to switch between them
Web users may have noticed over the last year or so more and more web addresses shifting from HTTP to HTTPS. These two main methods for transferring data across the internet and the World Wide Web are known as the Hypertext Transfer Protocol (HTTP) and the Hypertext Transfer Protocol Secure (HTTPS).
As you might well imagine, HTTPS has added an extra layer of security to web browsing than HTTP, with anybody and everybody’s browsing data now protected through encryption. The traditional HTTP method transmitted information as clear for all to see as if it was jotted down onto a piece of paper.
The new protocol uses secure socket layer (SSL) and transport layer security (TLS) to encrypt any information being transmitted, meaning that it’s relatively difficult, if not impossible, to read if and when intercepted. Any attackers hoping to glean information from such data will instead be met with garbled letters and numbers.
HTTPS was traditionally used to protect highly sensitive information, such as online payments since it was conceived 26 years ago by Netscape for the Netscape Navigation web browser. In recent history, however, it’s been rolled out to almost all online platforms and has overtaken HTTP as the most common method of web-based data transfer.
What are the benefits of HTTPS over HTTP?
As mentioned above, using HTTP means data is transmitted in plain text. This means that if someone were to intercept that data while it's in transit known as a man-in-the-middle attack they would be able to see all of it without putting in any additional effort.
HTTPS, meanwhile, uses public key encryption via SSL/TLS to thwart this kind of attack.
Network services provider Cloudflare gives the following example: When using HTTP to send the message "Hello World!", the attacker would see exactly that, plus some additional information about the server, when the text was created and so on.
With HTTPS, it would see something like the following:
Additionally, in order for a website to have the SSL certificate that enables it to use HTTPS, the domain must be verified to check that it belongs to the website owner and in some cases, legal certificates must be presented to verify everything is in order.
HTTPS will also improve a website's ranking on Google, only the best and most secure get to feature on the first page and statistics show that 84% of shopper will abandon a purchase if they don't see the little green padlock next to the URL.
How to switch from HTTP to HTTPS
If you're not yet using HTTPS to secure your website, it's time to talk to your hosting company, which should issue and install an SSL certificate for you, redirecting your traffic from the HTTP to the https version with little effort.
If this isn't the case, there are plenty of third-party companies that you can purchase an SSL certificate from and then manually set it up on your FTP. You will then need to set up a redirect to tell browsers trying to access the HTTP version of the site to HTTPS.
Key considerations for implementing secure telework at scale
Identifying the security risks and advanced requirements of a remote workforceDownload now
The State of Salesforce 2020
Your guide to getting the most from SalesforceDownload now
Fast, flexible and compliant e-signatures for global businesses
Be at the forefront of digital transformation with electronic signaturesDownload now
Rethink your cybersecurity strategy for the new world
5 steps to secure the enterprise and be fit for a flexible futureDownload now