For example, imagine you're logging into a website.

Without appropriate encryption, sensitive information could be exposed while being transmitted.

With HTTPS:

Browser

↓

Encrypted communication

↓

Server

The goal is to prevent others on the network from simply reading the transmitted data.

🔐 HTTP vs HTTPS

HTTP: Not encrypted by TLS, Less suitable for sensitive communication, Uses http://

HTTPS: Encrypted using TLS, Protects data in transit, Uses https://

Modern websites should generally use HTTPS.

You'll learn more about certificates, TLS, and web security later.

🔒 What Does HTTPS Protect?

HTTPS helps protect data in transit.

For example:

Login information

Payment information

Personal information

API communication

It doesn't mean the entire application is automatically secure.

A website can still have vulnerabilities even when it uses HTTPS.

That's an important distinction.

🧩 HTTP in a Real Application

Suppose you're using a food delivery application.

You click:

"Order Now"

A simplified process could be:

Browser

↓

POST /orders

↓

Server

↓

Process order

↓

Database

↓

Server

↓

201 Created

↓

Browser

The browser and server communicate using HTTP.

Later, we'll learn how to build these requests ourselves using JavaScript.

🔄 Quick Revision

Remember these five ideas:

HTTP → Rules for communication between clients and servers.

Request → Sent by the client.

Response → Sent by the server.

HTTP methods → Describe the intended operation, such as GET, POST, PATCH, and DELETE.

HTTPS → HTTP communication protected using TLS encryption.

A simple picture:

Browser

↓

HTTPS Request

↓

Server

↓

HTTPS Response

↓

Browser

📝 Double Tap ❤️ For Part-7