Internet & HTTP Basics: How the Web Communicates

When you use a browser to view a website or click a button inside a mobile app, you are initiating a structured conversation across a worldwide grid of computers. But how do two computers separated by thousands of miles agree on how to exchange messages?

The answer lies in the combination of physical networking (the Internet) and application communication rules (HTTP). By the end of this guide, you will understand exactly how data packets travel across routers, resolve DNS addresses, formulate HTTP headers, store cookies, and return status codes.

The Internet (short for Interconnected Networks) is a massive, decentralized global system of interconnected computer networks. It links billions of devices — from personal smartphones and laptops to cloud servers, supercomputers, and smart home appliances.

The Internet works through a concept called Packet Switching. When you send a photo or load a webpage, the file is broken into thousands of tiny chunks called data packets.

Each packet contains the destination IP address and its sequence number. Packets travel independently across multiple paths and routers, and your computer reassembles them in perfect order upon arrival!

Remember this golden rule:

Your device connects to your local router via Wi-Fi radio waves or Ethernet cable. The router connects to a modem, which translates digital data into optical light pulses over fiber cables to your Internet Service Provider (ISP). Your ISP connects to global Tier-1 Internet backbone providers.

An IP (Internet Protocol) Address is a unique numerical label assigned to every device connected to a computer network.

Just as postal mail cannot be delivered without a street number and zip code, Internet data packets cannot reach your screen without knowing your IP address.

A Domain Name is a human-friendly alias for a numerical IP address (for example, google.com or pathubs.com).

The Domain Name System (DNS) is the worldwide distributed database that maps domain names to IP addresses. It functions as the phonebook of the entire Internet.

A Client is any device or software application that requests services or content over a network. Your web browser (Chrome, Safari, Firefox), mobile app, or terminal command line (curl) acts as an HTTP client.

A Server is a high-performance computer running specialized software that waits 24/7 for client requests, processes application logic, and serves back responses.

Communication is strictly structured into Request-Response pairs: the client asks a specific question or sends data (Request), and the server answers with the result (Response).

A Protocol is an agreed-upon set of rules determining how data is formatted, sent, received, and acknowledged between computing systems. Without protocols, machines built by different companies speaking different operating systems could not understand each other.

HTTP is the application-level protocol that powers the entire World Wide Web. It defines how web browsers request web documents and how web servers deliver them.

HTTP was created in 1989 by Tim Berners-Lee to provide a simple, universal, and stateless protocol for fetching linked HTML research documents across distributed networks.

An HTTP Request is the message sent by the client to trigger an action on the server (viewing a page, submitting a form, deleting an account).

An HTTP Response is the reply packet delivered by the server containing a status code, response headers, and the requested content payload.

Every HTTP request contains four fundamental components:

Request Method

Specifies the desired action: GET, POST, PUT, PATCH, DELETE.

URL (Path)

The exact resource route on the server (e.g. /api/login or /explore).

Headers

Metadata key-value pairs (e.g. Host: pathubs.com, User-Agent, Authorization: Bearer token).

Body (Optional)

The payload data (usually JSON or form-data) sent during POST, PUT, or PATCH requests.

Every HTTP response contains three main parts:

Status Code

A 3-digit number informing the client of the outcome (e.g. 200 OK, 404 Not Found, 500 Server Error).

Response Headers

Metadata including Content-Type: text/html, Set-Cookie, and Cache-Control.

Response Body

The actual HTML, CSS, JavaScript, image, or JSON data delivered to the client.

Headers provide instructions on how to handle the connection:

• Content-Type: application/json — Declares the MIME format of the data.
• Authorization: Bearer [token] — Passes authentication credentials.
• Cache-Control: max-age=3600 — Informs the browser how many seconds to cache the response.
• User-Agent — Identifies the client operating system and browser version.

Because HTTP is stateless (the server forgets you the instant a request finishes), servers use Cookies to remember logged-in users:

1. 1. You log in with your username and password.
2. 2. Server validates credentials and returns a header: Set-Cookie: session_id=xyz789; HttpOnly; Secure.
3. 3. Your browser saves the cookie and automatically attaches Cookie: session_id=xyz789 to all future requests.

The moment you hit Enter in your browser:

• 1. URL is parsed and local DNS cache is checked.
• 2. DNS queries find the server IP address.
• 3. TCP 3-Way Handshake + TLS 1.3 encryption handshake are performed.
• 4. HTTP GET request is sent across the Internet backbone.
• 5. Server processes request and returns HTTP 200 with HTML/JSON.
• 6. Browser parses HTML and paints the page to screen.

When you submit a login form on Pathubs:

• 1. JavaScript intercepts the form submit event and collects your email.
• 2. It sends an encrypted POST /api/login request with JSON body.
• 3. Server hashes the password and validates your account in PostgreSQL.
• 4. Server replies with HTTP 200 OK and a Set-Cookie: session_token=... header.
• 5. Browser redirects you to your personalized learning dashboard!

You now have a deep, practical understanding of how computers connect across the Internet and exchange structured messages using HTTP and HTTPS.

With networking and communication protocols mastered, the next topic explores Browser Basics & Developer Tools, where you will learn how to inspect network packets and debug real-time web applications directly in Chrome DevTools!