Skip to content
BENIBIX Learn

HyperText Transfer Protocol (HTTP)

Infrastructure🌐 NetworkingWeb Protocols

Also known as HTTP, HTTP/1.1, HTTP/2, HTTP/3

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

Think of it like

Think of it like ordering at a counter. You ask the same way each time, and get the same kind of reply.

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.

Definition

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.

Common mistake

Sending passwords over plain HTTP. Anyone on the network can read them. Use HTTPS.

Key takeaways

  1. 1
    Request and response. The browser asks, the server answers.
  2. 2
    Each request alone. No memory between them.
  3. 3
    Not encrypted. HTTPS adds that.

Compare

Learn it properly