Learn
5.1.1–3 | INTERNET AND THE WEB
01 | THE INTERNET IS THE INFRASTRUCTURE
The internet is a worldwide network of interconnected networks. It links devices and networks so data can be exchanged using agreed communication protocols.
Its infrastructure includes communication links, routers and other network equipment. Data can travel through wired or wireless connections and across several networks to reach its destination.
Think of the internet as the communication system. It is not just a collection of web pages and it is not the same thing as a browser.
Web browsing, email, file transfer and many online games use internet communication. The web is one use of this infrastructure.
02 | THE WORLD WIDE WEB IS A SERVICE
The World Wide Web (WWW) is the collection of websites and web pages accessed using the internet. Web resources are connected through hyperlinks and identified by addresses.
A website is a related collection of web pages and resources. A web page is an individual document that a browser can display, normally using HTML along with other resources.
For example, Computer Science Café is a website. This lesson is one page within it. The internet provides the connection used to request the page from its server.
Key difference: the internet is the infrastructure; the web is a service using it.
03 | KEEP THE ROLES SEPARATE
| Term | Role | Example |
|---|---|---|
| Internet | Interconnected network infrastructure | Networks and routers carrying a request |
| World Wide Web | Websites, pages and linked resources | An online lesson and its hyperlinks |
| Web browser | Client software that requests and displays web content | A browser running on a student’s laptop |
| Web server | A system that responds to requests for web resources | The server hosting the lesson |
A browser is not the internet. It uses a network connection and web protocols to communicate with servers. A web server is not the whole web; it serves particular resources.
Email can use the internet without being a web page. A webmail interface adds a web-based way to access email, showing that services can work together.
04 | WHAT IS A URL?
A uniform resource locator (URL) is a text-based address used to locate a resource. In this syllabus, focus on the address of a web page.
A web URL can contain the protocol, domain name and web page or file name. A path can organise the resource into directories.
https://www.computersciencecafe.com/511---513-the-internet-cie.html
| Part | Example | Meaning |
|---|---|---|
| Protocol / scheme | https | Use HTTPS for the request |
| Domain / host name | www.computersciencecafe.com | Identify the host to contact |
| Path and page name | /511---513-the-internet-cie.html | Identify the requested page on that host |
The :// follows the scheme. The slash after the host begins the path. A URL is not simply another term for an IP address.
05 | READ A SECOND URL
Consider this invented teaching URL:
https://learn.example.org/courses/lesson.html
PROTOCOL
https://DOMAIN / HOST
learn.example.orgPATH / PAGE
/courses/lesson.htmlThe requested file name is lesson.html, within the courses path. The host name includes the learn subdomain.
Not every page address ends in .html. Servers can provide resources at other paths. A URL may also contain extra parts such as a query or fragment; these do not remove the core distinction between host and path.
06 | HTTP: RULES FOR WEB REQUESTS
Hypertext Transfer Protocol (HTTP) defines how a client and server exchange web requests and responses.
A browser acts as a client. It requests a resource, for example a page. The server sends a response containing information about the result and, where appropriate, the requested content.
GET is a common request method used to retrieve a resource. A response can include a status such as 200 OK for success or 404 Not Found when the requested resource is unavailable at that address.
HTTP does not itself supply transport encryption. Plain HTTP traffic can expose content to someone able to observe the connection.
07 | FOLLOW A PAGE REQUEST
- The user chooses a URL.
The browser identifies the scheme, host and requested path.
- The browser establishes communication.
The host name is normally resolved to a suitable IP address and the browser connects to the server.
- The client sends a request.
For example, it requests the lesson path using HTTP.
- The server returns a response.
It supplies a status and, if successful, the page content.
- The browser displays the page.
It interprets HTML and may request additional resources such as stylesheets and images.
This is a simplified example. Caching can reduce the need to fetch a resource again. A single page view often involves several requests, rather than one file containing every part of the page.
DNS and browser functions are explored further in later lessons.
08 | HTTPS: HTTP WITH TRANSPORT SECURITY
Hypertext Transfer Protocol Secure (HTTPS) uses HTTP with a secure, encrypted connection, normally provided by TLS.
Before exchanging web content, the client and server establish the secure connection. The browser checks the server’s certificate against the requested host and trusted certificate information, as part of authenticating that server.
The secure connection protects the confidentiality of exchanged content and helps protect its integrity, making undetected changes in transit harder.
The browser and server must still process the readable content at their endpoints. HTTPS protects transport; it does not mean the page is stored as unreadable text forever.
09 | WHY HTTPS MATTERS
Suppose a student submits login details to a website. With plain HTTP, an observer able to monitor the connection may be able to read the transmitted information.
HTTPS encrypts the exchange, so an observer cannot simply read the page content or submitted details from the network traffic. Integrity protection also helps detect tampering.
HTTPS does not guarantee an honest website. A phishing site can also use HTTPS. Certificate checks authenticate the connection to the named host; they do not approve the site’s claims or intentions.
Other information, such as some connection metadata, may remain observable. Do not claim HTTPS hides every aspect of internet activity.
10 | COMPARE HTTP AND HTTPS
| Point | HTTP | HTTPS |
|---|---|---|
| Purpose | Exchange web requests and responses | Exchange web requests and responses securely |
| Scheme | http:// | https:// |
| Transport encryption | Not provided by plain HTTP | Provided through the secure connection |
| Protection in transit | Content may be readable or modified by an observer in a suitable position | Confidentiality and integrity protection |
| Trust limit | Protocol use does not prove the site is honest | Encryption and certificate checks do not prove the site is honest |
Exam-style explanation: HTTPS encrypts data exchanged between the client and server, making it harder for an observer to read sensitive information in transit. It also protects integrity and checks server identity through certificates.
11 | CONNECT THE IDEAS
A URL tells the browser which host and resource to request and which scheme to use. The internet carries communication between networks. HTTP defines the web request and response. HTTPS protects that exchange through a secure connection.
The resulting page belongs to the web. The browser is the software that requests and displays it. These are related ideas, but they are not interchangeable terms.
12 | COMMON MISTAKES
- The web and internet are identical: distinguish the service from the infrastructure.
- A browser is a network: it is client software.
- A URL is only a domain: it can also specify a scheme and resource path.
- HTTP is HTML: HTTP exchanges resources; HTML describes page structure.
- HTTPS makes a website honest: it protects the connection, not the site’s intentions.
- One page always means one request: images and stylesheets may need additional requests.
- HTTPS hides all metadata: transport encryption does not conceal everything.