HTTP (Hypertext Transfer Protocol) is the foundation of data communication on the World Wide Web. It defines how clients (browsers) request resources and how servers respond.
GET (retrieve), POST (send data), PUT (update), DELETE (remove)HTTPS (HTTP Secure) = HTTP + TLS (Transport Layer Security):
| HTTP | HTTPS | |
|---|---|---|
| Port | 80 | 443 |
| Encryption | None | TLS (symmetric session key) |
| Authentication | None | Digital certificate (CA-signed) |
| Use case | Static public content (deprecated) | All modern web traffic |
FTP is used to transfer files between a client and a server. It uses two separate connections:
FTP transmits data in plaintext — login credentials are visible. SFTP (SSH File Transfer Protocol, port 22) and FTPS (FTP over TLS) add encryption. For the exam, know that standard FTP is unencrypted.
Active vs Passive mode: In active mode, the server initiates the data connection back to the client — this is often blocked by firewalls. In passive mode, the client initiates both connections — friendlier for firewalls/NAT.
Three separate protocols handle email — one for sending and two for receiving:
| Protocol | Port | Purpose | Key behaviour |
|---|---|---|---|
| SMTP | 25 (or 587 with auth) | Sending email — from client to mail server, and between mail servers | Push protocol — messages pushed from sender to server |
| POP3 | 110 | Receiving email — downloads to local device | Downloads and (by default) deletes from server. Email exists only on client. Simple but not multi-device friendly. |
| IMAP | 143 | Receiving email — synced with server | Email stored on server; client shows a synced view. Supports multiple devices. Folder structure, read status all synced. |
SMTP (Simple Mail Transfer Protocol) is responsible for all outbound email delivery. When you send an email:
| POP3 | IMAP | |
|---|---|---|
| Storage | Downloads to client, deletes from server | Stored on server; client shows synchronised view |
| Multi-device | Poor — only available on one device | Excellent — all devices see same emails |
| Offline | Works offline (email downloaded) | Requires connection to view (unless cached) |
| Server storage | Low (deleted after download) | Higher (all emails stored server-side) |
| Use case | Single device, low server storage | Multi-device (phone + laptop + webmail) |
HTTP follows a simple request-response cycle:
GET /index.html HTTP/1.1 to the server.HTTP/1.1 keeps the connection open (persistent) for multiple requests. HTTP/2 and HTTP/3 add multiplexing (many requests simultaneously on one connection).
8 questions · 20 marks · instantly marked
| Term | Definition |
|---|