[5.1.1–4] Internet vs WWW; URLs; HTTP/HTTPS; browsers

Internet vs World Wide Web, URLs, HTTP/HTTPS and Web Browsers

Big picture: how the pieces fit together

The internet is a global network of networks. It is the physical and logical infrastructure that links millions of devices together using agreed rules called protocols. Cables, Wi-Fi, mobile data, routers and switches are all part of the internet. By contrast, the World Wide Web (WWW) is a service that runs on top of the internet. The web uses the internet to send and receive webpages, media and data using the HTTP or HTTPS protocols. Not everything that uses the internet is the web. Email, video calls and online gaming use other internet services and protocols.

When you type a URL into a web browser, the browser uses HTTP or HTTPS to request resources such as HTML, images and scripts from a web server. The server responds with a status code and the resource data. The browser then renders the page, applies styles, runs scripts and allows you to interact by following links or submitting forms. Understanding where the internet ends and the web begins helps students explain why some problems are due to connectivity while others are due to website or browser issues.

Internet vs Web: clear distinctions

The terms are often mixed up in everyday speech, but they refer to different concepts. Use the tabs to compare and reinforce the differences with concrete scenarios.

The internet is the global network that connects computers and devices. It relies on hardware such as routers and switches and on core protocols like TCP/IP and DNS. It carries many different types of traffic, not only web pages. Think of the internet as the road system that allows many kinds of vehicles to travel to many destinations.

The web is a hypertext system of linked resources accessed with browsers. It uses HTTP or HTTPS to fetch web resources (HTML, CSS, images, scripts) from servers. Many other applications use the internet but are not the web, for example email (SMTP/IMAP), file transfer (FTP/SFTP) and messaging apps using their own protocols.

  • Scenario A: Your internet connection is down at home. Nothing that uses the internet works: no email, no browsing, no streaming. This is an internet problem.
  • Scenario B: The internet connection is fine but a specific website will not load and returns an error. Other sites work. This is likely a web server or website problem, not the general internet.
  • Scenario C: Your game updates download successfully but you cannot open any webpages due to a misconfigured browser proxy. The internet is functioning, but your browser settings block web access.

URLs: how web addresses are structured

What a URL tells the browser

A Uniform Resource Locator (URL) provides all the information a browser needs to find and request a specific web resource. A typical URL has these parts:

  • Scheme: the protocol used, usually http or https.
  • Host name: the server domain, for example www.example.org.
  • Port (optional): the network port number, for example :443 for HTTPS. When omitted, a default is assumed by the scheme.
  • Path: the location of the resource on the server, for example /learn/topics.
  • Query string (optional): key–value data after ?, such as ?page=2&sort=latest.
  • Fragment (optional): an anchor after # to jump to a section within the page, for example #glossary.

Browsers also rely on DNS (Domain Name System) to translate a domain name into an IP address so that packets can be routed to the correct server on the internet.

https://www.example.org/

  • Scheme: HTTPS (encrypted web)
  • Host: www.example.org
  • Path: / (the root of the site)
  • No explicit port (defaults to 443 for HTTPS)

https://shop.example.org/products?category=laptops&sort=price#reviews

  • Scheme: HTTPS
  • Host: shop.example.org
  • Path: /products
  • Query: category=laptops, sort=price
  • Fragment: reviews (browser scrolls to the reviews section after loading)

http://intranet.school.local:8080/noticeboard/today

  • Scheme: HTTP (not encrypted)
  • Host: intranet.school.local
  • Port: 8080 (chosen by the site administrator)
  • Path: /noticeboard/today

HTTP and HTTPS: how the web communicates

Purpose of HTTP

HyperText Transfer Protocol (HTTP) defines how a client (usually a browser) requests resources from a server and how the server replies. The client sends a request with a method such as GET (retrieve a resource) or POST (send data, e.g. from a form). The server sends a response with a status code such as 200 (OK), 404 (Not Found) or 500 (Server Error), along with the data and headers that describe the content type and caching rules.

Why HTTPS is necessary

HTTPS is HTTP with encryption and authentication provided by TLS (Transport Layer Security). Encryption protects privacy by preventing others on the network from reading or altering the data in transit. Authentication helps the browser verify that it is talking to the genuine server for that domain name. Modern browsers display a padlock icon for valid HTTPS connections and show clear warnings if security checks fail.

  1. Browser resolves the domain name to an IP address using DNS.
  2. Browser connects to the server's HTTP port (default 80).
  3. Browser sends a GET request for a resource path.
  4. Server replies with a status code and the resource data.
  5. Anyone who can observe the traffic could read or modify it because it is not encrypted.
  1. DNS resolution as before, then the browser connects to port 443 (HTTPS).
  2. A TLS handshake sets up encryption keys and the server presents a digital certificate.
  3. The browser checks the certificate is valid, not expired and issued for the correct domain by a trusted authority.
  4. If checks pass, an encrypted channel is created and HTTP requests and responses travel securely inside it.
  5. People on the network can see that a connection exists but cannot read the content.

If the certificate is invalid or the domain does not match, the browser shows a clear warning. Causes include an expired certificate, someone intercepting traffic or a user entering the wrong address. The safe action is to stop and verify the URL or contact the site owner. Proceeding may expose private data.

Web browsers: purpose and key functions

What a browser does

  • Fetches resources using HTTP/HTTPS as directed by URLs and links.
  • Renders HTML and CSS to display pages and applies layout and styling rules.
  • Executes client-side scripts (for example JavaScript) to handle interactivity.
  • Manages security: enforces the same-origin policy, validates HTTPS certificates and blocks mixed content where needed.
  • Provides user tools such as bookmarks, history, downloads, private browsing and developer tools for diagnostics.
  • Caches resources to speed up repeat visits while respecting server caching policies.

How browsers improve performance and reliability

  • Caching: stores copies of images and scripts locally to avoid repeated downloads.
  • Preloading and prefetching: begins fetching likely next resources to make navigation feel quicker.
  • Error handling: shows status messages, suggests reloading and can recover tabs after a crash.
  • Extensions: optional add-ons that add features such as translation or password management. Schools should manage extensions to maintain safety and performance.

Deep Dive: Status codes and what they mean

2xx success codes (such as 200 OK) indicate the request worked. 3xx redirection codes (for example 301 Moved Permanently, 302 Found) tell the browser to request a different URL. 4xx client error codes indicate a problem with the request, such as 404 Not Found or 403 Forbidden. 5xx server error codes indicate the server encountered a problem fulfilling a valid request. Knowing the category helps students diagnose whether the issue is likely on the user side or the server side.

Summary of terminology

Term Short definition
Internet Global network infrastructure that connects devices and transports data using protocols like TCP/IP.
World Wide Web (WWW) Service that uses the internet and HTTP/HTTPS to access and link web resources.
URL Uniform Resource Locator: the address that tells a browser where and how to fetch a resource.
HTTP Application protocol for requesting and delivering web resources without encryption.
HTTPS HTTP over TLS providing encryption and server authentication for secure communication.
TLS Security protocol that provides encryption and authentication for HTTPS connections.
Browser Client application that fetches, renders and interacts with web content securely and efficiently.
Status code Numeric code in a server response indicating the outcome of a request (e.g. 200, 404).

 Key Takeaways

  • The internet is the worldwide network infrastructure; the web is a hypertext service that runs on it using HTTP/HTTPS.
  • URLs describe the scheme, host, path and optional query or fragment so a browser can fetch the correct resource.
  • HTTP defines request and response rules; HTTPS adds TLS encryption and authentication for privacy and trust.
  • Browsers fetch, render and secure web content and include tools such as caching, history, bookmarks and developer tools.
  • Status codes help diagnose problems by showing whether an issue is on the client side (4xx) or server side (5xx).