What is the World Wide Web?
Typing a search word and clicking a link feels effortless, but it relies on a simple idea: hyperlinked documents running on top of the Internet. Here is a lightweight tour of how the Web is layered and what to watch for when it misbehaves.
So, what is the WWW?
The Web is a system of documents connected by hyperlinks. It rides on the Internet and ships information using HTTP and HTML.
Web vs. Internet
- Internet: the physical and logical network (IP, routers, fiber) that moves packets.
- WWW: the delivery rules (HTTP/HTTPS) and document format (HTML) that sit on that network. Mail, FTP, SSH, and other protocols coexist on the Internet but are not part of the Web.
Three ingredients of the Web
- URL/URI: the address that says where a resource lives.
- HTTP: the delivery protocol that carries the request to that address.
- HTML + links: the human-friendly document that points you to the next place.
Looking at a URL
The address bar exposes clues about where you are going and whether it is safe.
URL anatomy
| Part | Example | Meaning |
|---|---|---|
| Scheme | https | How to talk to the server. HTTP/HTTPS dominate the Web. |
| Host | www.example.com | A host name or IP address. Names with and without www are distinct; serving the same site requires configuration. |
| Path | /docs/www | Identifies a resource; it need not be a filesystem location. |
| Query | ?q=web | Extra parameters; search and filters love this. |
| Fragment | #what-is | A position or other client-side identifier, omitted from the normal HTTP request. |
What happens when you click a link
- The browser resolves the host name to an IP via DNS (using cache when possible).
- For a new HTTPS connection, it negotiates TLS and checks certificate identity, trust, and validity. Existing connections may be reused.
- It sends an HTTP request (GET/POST and headers).
- The server replies, then the browser fetches HTML/CSS/JS/images as needed to render the page.
HTTP basics
HTTP exchanges requests and responses whose meanings are independent. Applications can still keep state with cookies and server-side sessions. Request information can be carried in the URL, headers, and content; it is not all placed in headers.
Requests and responses
- Methods: GET for retrieval, POST for submit/create, PUT/PATCH/DELETE for updating APIs.
- Headers: User-Agent, Accept, Cookie, and cache directives tell the server how to respond.
- Responses include a status code and headers. Some, including responses to HEAD and 204 or 304 responses, have no content.
Remembering state
- Cookies: tiny pieces of data stored by the browser and sent back, often holding a session ID.
- Caching: Cache-Control and ETag allow clients to reuse resources to save time and bandwidth.
- Redirects: 301/302/307/308 steer the browser to another URL (HTTPS enforcement, www/non-www alignment).
Common status codes
| Code | Meaning |
|---|---|
| 200 OK | All good. |
| 301/302 | 301 is a permanent move; 302 is temporary. |
| 304 | Not modified; you can keep your cached copy. |
| 400/403/404 | Bad request / forbidden / not found. |
| 500/503 | Server-side issue such as errors or maintenance. |
The Web today
Browsing feels effortless because the ecosystem has moved to safer, faster defaults. A few trends are worth noting.
HTTPS by default
- Expired certificates can prevent connections. Automated renewal together with failure monitoring reduces missed renewals.
- Major browsers normally use HTTP/2 over HTTPS, but the HTTP/2 specification also permits cleartext TCP. HTTP/3 uses QUIC with TLS. Performance gains depend on the environment.
- HSTS and redirects commonly force HTTP traffic onto HTTPS.
Web beyond the browser
- Mobile apps and IoT devices call HTTP(S) APIs to fetch or update data.
- Web APIs that return JSON or XML (not HTML) still follow the same URL design and caching principles.
Privacy shifts
- Third-party cookie handling varies by browser and settings. Cookie availability alone does not establish user counts or whether tracking is possible.
- Tracking protections may strip referrers or user agent details, so analytics configuration matters.
Quick tips
A few reminders that help when designing links or debugging odd behavior.
When things break
- First compare a reload or a separate browser profile. If needed, clear site-specific cache and cookies, remembering this may log you out or remove preferences.
- DNS changes take time to propagate; use dig to see what you actually resolve.
- Check certificate validity, host identity, and intermediates. Do not bypass certificate warnings.
- Watch for same-origin policy or CORS blocking requests across domains or subdomains.
Link design
- Aim for stable permalinks; use 301 redirects when moving content.
- Fragments (#id) enable deep links into long pages and make sharing easier.
- Tune metadata like OGP so previews look good on social or search results.
Specifications and related reading
RFC 9110: HTTP Semantics / RFC 9113: HTTP/2
HTTP basics / HTTP versions / DNS basics