RoadToWebDev Day#2 — HTTP/HTTPS and APIs

This is a part of my ongoing series about exploring the Road To Web Development, you can find rest of the blogs here

What is HTTP?

HTTP is the HyperText Transfer Protocol. HyperText is a series of text documents that are linked to each other via hyperlinks. HTTP is used to transfer the hypertext from the web-server to your browser so that it can be viewed. With the help of hyperlinks, you are able to navigate among other webpages. Hence, the main job of HTTP is to transfer information like documents, images, videos, or files from the web-server to your web browser.

What is HTTPS?

Let us start with an example. If we want to log in to the Gmail account, we need to enter private details so we need to be sure that our information is passed on to the web-server in a secured way. For that, HTTPS ie. HyperText Transfer Protocol Secure is used. So, basically, HTTPS is a secured version of HTTP. HTTPS prevents our private information such as usernames or passwords to be leaked. HTTPS uses an encryption protocol in order to pass the information in a secured manner to the web-server.

What is an API?

API stands for Application Programming Interface. API helps different applications to communicate with each other. Let us take an example: If you are interacting with an application through your mobile phone, the application connects to the internet and sends the data to the server. Then the server interprets the data and performs the required tasks according to the requests and sends the data back to the mobile phone. Finally, the application represents the required data in a readable form to the user. Each of these transactions of data is done with the help of API.

I have found a good explanation of API and REST API on the below-mentioned video. You may find it helpful.