CIE IGCSE | 5.1.5 Web Protocols

Lesson objective

Describe how a page is located, retrieved and displayed after entering a URL, including the roles of the browser, DNS, IP addresses, web server and HTML.

Learn

5.1.5 | WEB PROTOCOLS

01 | WHAT THIS LESSON CONNECTS

When you enter a URL, the browser must identify the resource, locate the server, request the content and display the result.

This lesson is labelled Web Protocols in the course navigation. The specification’s central requirement is to describe how a web page is located, retrieved and displayed, including the browser, IP addresses, DNS, the web server and HTML.

DNS and HTTP have different jobs: DNS helps resolve a host name to an address; HTTP defines the web request and response. Neither is the page’s markup language.

02 | START WITH THE URL

Use this invented teaching URL:

https://learn.example.org/courses/lesson.html

The host locates the service; the path selects the resource
ComponentValueWhat the browser needs it for
SchemehttpsChoose secure web communication
Host namelearn.example.orgIdentify the host whose address is needed
Path/courses/lesson.htmlIdentify the requested resource at that host

DNS does not look up the whole URL including its page path. The browser normally asks for address information associated with the host name.

03 | WHY AN IP ADDRESS IS NEEDED

An IP address identifies a network interface or destination for IP communication. Routers use destination IP information to forward packets towards the appropriate network.

People often find names easier to remember than numeric addresses. The browser therefore needs a way to obtain an appropriate address for the host name.

For this lesson’s example, suppose the host resolves to 192.0.2.25. This is an illustrative address, not a claim about the real location of a website.

A host can have several addresses, and an address can support several websites. Do not assume every domain has exactly one permanent IP address.

04 | DNS: RESOLVE THE HOST NAME

DNS stands for Domain Name System. A domain name server provides DNS information used to resolve names.

In the simple teaching model, the browser’s device requests the IP address associated with the host name. A DNS server returns suitable address information, enabling communication with the web service.

DNS is a distributed system, not one server holding every answer. A resolver may consult other DNS servers to obtain the required information.

The browser, device or resolver may already have a valid cached answer. In that case, a fresh lookup through the full DNS system is not always necessary.

05 | DNS DOES NOT SEND THE WEB PAGE

DNS LOOKUP

Question: what address is associated with learn.example.org?

Answer in this example: 192.0.2.25

WEB REQUEST

Question: provide /courses/lesson.html on that host.

Answer: a web response, including the page if available.

The DNS service supplies name-resolution information. The web server supplies the requested web resource. These are distinct roles even if services are hosted on related infrastructure.

06 | ESTABLISH COMMUNICATION

With suitable address information, the browser establishes communication with the server. For an HTTPS URL, a secure connection is set up before the web content is exchanged.

Certificate checks help authenticate the server for the requested host. Encryption and integrity protection help protect the exchange in transit.

The IP address guides network delivery; the host name remains important for selecting and authenticating the intended web service.

You do not need to memorise transport-handshake details for this syllabus point. Focus on the roles and the order of the main steps.

07 | SEND THE WEB REQUEST

The browser sends an HTTP request for the resource. A common method for retrieving content is GET.

In our example, the request identifies /courses/lesson.html and the intended host. With HTTPS, the HTTP exchange is carried through the secure connection.

DNS has already served its purpose: it helped obtain the address. It does not search the server’s folders for the page.

08 | THE WEB SERVER RESPONDS

The web server processes the request and returns a response. A successful response can include the requested HTML; an unsuccessful response can indicate a problem.

A response contains status information and content where appropriate
Example statusMeaning
200 OKThe request succeeded
404 Not FoundThe requested resource was not found at that address
Redirect responseThe client is directed towards another resource address

A server may supply an existing HTML file or generate content using server-side software. The browser receives the resulting response, not necessarily the server’s original source program.

09 | HTML AND DISPLAY

HTML describes page structure, such as headings, paragraphs and links. The browser processes it to create the displayed page; this is rendering.

The HTML may refer to other resources such as a stylesheet, an image or a script. The browser can send additional requests to retrieve them.

CSS helps control presentation; client-side JavaScript can add behaviour. The display may develop as resources arrive rather than appearing through one universal all-at-once process.

HTTP is not HTML: HTTP governs the exchange, while HTML describes the document returned through it.

10 | THE WHOLE SEQUENCE

  1. Read the URL.

    The browser identifies the scheme, host and resource path.

  2. Resolve the host name.

    DNS supplies suitable IP address information, unless a usable cached answer is already available.

  3. Connect to the server.

    The browser establishes communication; HTTPS adds a secure connection.

  4. Request the resource.

    The client sends an HTTP request for the path on the intended host.

  5. Receive the response.

    The web server returns status information and the available content.

  6. Render the page.

    The browser processes HTML and other resources, requesting additional files if needed.

Describe the sequence in connected sentences. Explain each role rather than just listing DNS, IP, HTTP and HTML.

11 | DIAGNOSE DIFFERENT FAILURES

These are possible explanations, not automatic proof of one exact fault
SituationPossible explanation
Host name cannot be resolvedA name or DNS problem prevents obtaining suitable address information
Connection cannot be establishedThe destination or network route may be unavailable
Server returns 404The server responds, but the requested resource is not found
Page text appears but an image is missingA separate resource request may have failed
Old content appearsA cached copy may be involved

A 404 response does not mean DNS necessarily failed: the browser has received a response from a web server. Separate steps can succeed or fail independently.

12 | COMMON MISTAKES

  • DNS downloads HTML: it supplies name-resolution information.
  • DNS resolves every character in a URL: the host name is the relevant lookup component.
  • The IP address identifies the page path: the request selects the resource on the host.
  • The web server displays the page on your screen: the browser renders the returned content.
  • HTTP and HTML are identical: exchange rules differ from document structure.
  • Every visit repeats a full DNS lookup: valid cached answers may be used.
  • A missing image proves the whole connection failed: individual resource requests can fail.

MATCH THE PAGE-RETRIEVAL ROLE

Terminology

Terminology

DNS

Domain Name System: the distributed system providing name-resolution information.

Domain name server

A server providing DNS information.

Resolver

A component that obtains DNS answers, potentially consulting other servers.

Host name

The name identifying the host in a URL.

IP address

An address used for IP communication and network delivery.

URL

A text-based resource address that can include scheme, host and path.

Path

The component selecting the resource within the host’s service.

Web browser

The client that requests and renders web content.

Web server

A system processing web requests and returning responses.

HTTP

Hypertext Transfer Protocol: rules for web requests and responses.

HTTPS

HTTP exchanged over a secure encrypted connection.

GET

An HTTP method commonly used to retrieve a resource.

Response status

Information indicating the result of a request, such as success or not found.

HTML

Hypertext Markup Language: markup describing page structure.

Rendering

Processing page code and resources into the displayed content.

Cache

Stored information reused when applicable, such as a valid DNS answer or resource copy.

Questions

Questions

CHECK YOUR UNDERSTANDING

Select all correct choices. Each exact set earns one point.

1. For https://learn.example.org/courses/lesson.html, which part is relevant to the DNS address lookup?
2. Which describe DNS correctly?
3. Which roles are correct?
4. Which statements about requests are correct?
5. Which statements about HTML and HTTP are correct?
6. The server returns 404. Which conclusions are reasonable?
7. Which cache statements are correct?
8. Which can occur while rendering?

EXPLAIN AND COMPARE

Write your answers before revealing each sample.

1. Describe the role of DNS after a user enters a web URL.

2. Explain why DNS and a web server have different roles.

3. Describe the sequence used to locate, retrieve and display a page.

4. Explain the roles of the IP address and resource path.

5. Compare HTTP and HTML in page retrieval.

6. Explain why a 404 response does not necessarily indicate a DNS failure.

7. Explain why a page can appear with a missing image.

APPLY IT | REPAIR THE EXPLANATION

A student says: “DNS finds the lesson file and displays its HTML. The browser sends the whole URL as an IP address.” Rewrite this accurately, keeping the roles separate.

Reveal suggested answer

DNS helps resolve the URL’s host name to suitable address information. The browser connects and sends a request for the resource path. The web server returns the page content, and the browser renders its HTML and other resources.

Flashcards

Flashcards

Click to flip. Select the ideas you need to revisit.

0 cards selected for revision.

    Selections are kept while this page is open.

    Workbook

    Workbook

    COMING SOON

    The workbook for 5.1.5 Web Protocols is coming soon. Complete the matching task and written questions in your exercise book.