21 Feb 2018


Often times when browsing, for whatever reason, we type in what we want in the search box but it seems the page we are looking for always add ‘https//’ just in front of the URL.

When do we get https? We get https whenever we are browsing the internet, and no matter or whatever we type, we get the http(s) in front of our URL. This abbreviation simply stands for Hypertext Transfer Protocol, while the ‘S’ at the end, is a secure version of the HTTP protocol.

HTTPS just like chrome or Microsoft edge sends a request for a content to a web server.  Just like when you type a specific word in your search tab, the HTTP, will help you request for the content of the word from a web page for you to see what you are searching for. 

The HTTP helps to interact with the World Wide Web but the sad part about this is that bad people can put all kinds of things into the browser, they can trick you to look at a site that is not what it claims, for example, some dubious ones can imitate bank websites and get you to enter your username and password. However, not to worry about this, Google is already making effort as it announced that sites not labelled with ‘S’ will be tagged insecure for web users to continue experiencing safer online experience.

Brief History of HTTP

The HTTP was created in the early 1990’s by Tim Berners-Lee and the HTTP0.9, HTTP 1.0, and HTTP 1.1 were the three versions deployed during that time. While the latest version is HTTP 2.0

The benefit of HTTPS is from encryption that is observers cannot see your information as it moves in the web search.  So, there is privacy between your data and the outside world. Even if you’re not sending sensitive data like personal info and passwords to an HTTP site, it’s still possible for outside observers to look at aggregate browsing data of the users and “deanonymize” their identities by analysing behaviour patterns.

For web developers, there are tools available to monitor HTTP communication. Like chrome/WebKit inspector,

If you are an individual or a business, and you want your site to get the HTTPS, Google has a site with specific instructions about how to switch to HTTPS by obtaining a security certificate. 

Most HTTP communication is initiated by a user agent and consists of a request to be applied to a resource on some origin server. In the simplest case, this may be accomplished via a single connection between the user agent and the origin server.  

Without the S after the HTTP however, web users need to be careful about these webs and this is why some browsers tell you a site isn’t secure whenever you are prompt to submit passwords. However, the extras ‘s’ in the HTTP plays an awesome role in websites.


Article by: Busayo Tomoh

Leave a Reply

Notify of