Skip to content
BENIBIX Learn

HTTP vs HTTPS

HTTP and HTTPS follow the same rules for asking for pages. HTTPS sends them over a locked line, so no one in between can read or change them. Plain HTTP can be read by anyone on the path.

Infrastructure🌐 Networking

HyperText Transfer Protocol (HTTP)

The rules for how a browser asks a server for a page.

HTTP is the set of rules browsers and servers use to talk on the web. The browser sends a request that names a page and a method, like GET. The server sends back a response with a status code and the page itself. Each request stands alone, so the server does not remember the last one unless told. Plain HTTP is not encrypted, which is why HTTPS exists.

Example
Emma clicks a link. The browser sends an HTTP request for /menu, and the server answers with the page and the code 200.
Why it matters
Every web page, image and API call travels over HTTP. Knowing it makes web bugs much easier to read.
Full entry
Infrastructure🌐 Networking

HyperText Transfer Protocol Secure (HTTPS)

HTTP sent over a locked line. No one in between can read or change it.

HTTPS is HTTP sent through a locked line, so no one in between can read or change it. It uses TLS to scramble the data and to prove the server is who it says it is. Browsers show a lock icon for HTTPS sites and warn on plain HTTP pages with forms. It uses port 443, where plain HTTP uses 80. Free certificates mean every site can and should use it.

Example
Lucy logs in to a bank at an https:// address. Someone on the same café Wi-Fi sees only scrambled data.
Why it matters
It keeps passwords, cards and private pages safe. Search engines also rank secure sites higher.
Full entry

In one line

HyperText Transfer Protocol (HTTP)
The rules for how a browser asks a server for a page.
HyperText Transfer Protocol Secure (HTTPS)
HTTP sent over a locked line. No one in between can read or change it.