Study Guide Instructor view
How a Web Page Is Loaded
Teaching notes for Lesson 4.7, with controls for presenting it.
Keep this page on your own screen. Share only the lesson window. The lesson window holds no teaching notes, so sharing it cannot show them.
Presenting
- Open the lesson in its own window and share that window, not this one.
- Use Next and Previous here, or the lesson’s own, to move through the lesson. Next reveals one thing at a time: the next idea, or the answer to the question on screen, then the next step. Previous takes the last reveal back. The line below says what is on screen and what Next will show.
- Reveal hints and answers when the class is ready, and reset a demonstration before using it again.
The controls need JavaScript and a browser that supports BroadcastChannel. Without them, open the lesson in presentation mode and use its own controls.
The two windows talk to each other only inside this browser, on this device. Nothing is sent to a server, and no account is needed. A second device (a phone or another tablet) cannot follow the lesson window yet.
Now on the lesson window
- On screen
- Next teaching point
Guidance for this point
Lesson plan
- Level
- Intermediate
- Time
- About 60 minutes; the steps below add up to 63
Learners predict what happens between pressing Enter and seeing a page, meet the DNS lookup as the missing step, and order the six events themselves before a step-through confirms the sequence. They then trace a request with fictional DNS records, work out why a failed lookup stops the journey, and move to cookies: how a website recognises a browser, the difference between session and persistent cookies, their uses, and their privacy considerations.
Objectives
- Put in order, and describe, the steps from entering a URL to seeing the page, naming the role of the browser, the DNS server, the IP address, the web server and HTML
- Explain why a browser needs the IP address and how a domain name server provides it
- Explain what a cookie is and how a website uses it to recognise a browser
- Distinguish session cookies from persistent cookies and give uses of cookies: saving personal details, tracking preferences, holding a shopping cart and storing login details
- Describe privacy considerations of cookies and choose a sensible response to a scenario
Before the lesson
- A browser on the shared screen, if available, to show the cookie settings page of the browser (without opening anyone's real data).
- Optional: index cards with the six events of the journey, one per card, for ordering in groups before the table task.
- A reminder of the previous lesson's URL parts, which the first step depends on.
Steps
Introduction Opening
On the lesson window now
On screen: the lesson’s title, module and number; Next adds its objectives and key terms, as the lesson page lists them; Next again begins the first step.
Objectives on screen
- Put in order, and describe, the steps from entering a URL to seeing the page, naming the role of the browser, the DNS server, the IP address, the web server and HTML
- Explain why a browser needs the IP address and how a domain name server provides it
- Explain what a cookie is and how a website uses it to recognise a browser
- Distinguish session cookies from persistent cookies and give uses of cookies: saving personal details, tracking preferences, holding a shopping cart and storing login details
- Describe privacy considerations of cookies and choose a sensible response to a scenario
Purpose: Learners predict what happens between pressing Enter and seeing a page, meet the DNS lookup as the missing step, and order the six events themselves before a step-through confirms the sequence. They then trace a request with fictional DNS records, work out why a failed lookup stops the journey, and move to cookies: how a website recognises a browser, the difference between session and persistent cookies, their uses, and their privacy considerations.
1. The pause before the page Think 5 min
On the lesson window now
Purpose: Surface learners' own model of what happens when a URL is entered, before any term is introduced, so that the later sequence corrects or extends it.
Ask
- List, in order, what you think happens between pressing Enter and the page appearing.
Responses to expect
- Most name the browser and a server; few name the DNS lookup
- Some say the page 'is found on the internet'
Misconceptions to challenge
- A learner may believe: “The browser already knows where every website is.” Respond: Ask how it would know the location of a site it has never visited. The next step answers it.
Checking understanding: Collect two or three different lists on the board without correcting them.
Depending on the answers
- If learners say the page just appears: ask where the page is stored and how the browser reaches that computer.
Discussion pause: One minute of silent writing; keep the lists to compare with the step-through.
In the lesson window
- Think it through: In that second, a lot of things must happen between the browser and other computers. List, in order, what you think happens between pressing Enter and the page appearing.
2. Names for people, numbers for computers Discover 8 min
On the lesson window now
Purpose: Use the contacts-list picture so that DNS is discovered as a need before it is named, then check the idea.
Ask
- What does the browser need before it can contact the website?
- What would the DNS server send back for www.example.org?
Responses to expect
- The IP address that goes with the name
- 203.0.113.25
Misconceptions to challenge
- A learner may believe: “The DNS server sends the page.” Respond: It holds names and addresses only. The page comes from the web server.
- A learner may believe: “A domain name and an IP address are the same.” Respond: One is readable by people; the other is the number computers use. DNS links them.
On the board or with the pen
- Draw a two-column table of names and numbers on the board and ask learners to look one up.
Checking understanding: The DNS check question: the 'HTML of the page' option diagnoses a mix-up between DNS and web servers.
Depending on the answers
- If learners say the router finds the IP address: recall that the router passes packets on; a DNS server holds the list of names and addresses.
English as an additional language
- Check 'record' and 'look up': a record is one line in a list.
In the lesson window
- Think it through: Mia typed a domain name, www.example.org. Computers on the internet are found by their IP addresses, which are numbers. What does the browser need to do before it can contact the website, and where might it get what it needs?
- Check your understanding: A browser asks a DNS server about www.example.org, using the records above. What does the DNS server send back?
3. Put the journey in order Predict 10 min
On the lesson window now
Purpose: Learners commit to an order for the six events using what they know, before the step-through reveals the answer, so that mistakes are informative.
Ask
- Which event must come before the browser can send its request?
- Why can the page not be rendered earlier?
Responses to expect
- The DNS reply with the IP address
- The HTML has not arrived yet
Misconceptions to challenge
- A learner may believe: “The request to the web server comes first, and the DNS lookup is done afterwards to find where to send it.” Respond: Ask how the request could be sent without a destination address.
On the board or with the pen
- Write the six events on cards or sticky notes on the board and let the class move them into order before revealing the step-through.
Checking understanding: The ordering table shows at a glance which step each learner misplaces; the step-through is then the check, not the first teaching.
Depending on the answers
- If the DNS steps are swapped with the request: ask what the browser holds at that moment: a name or a number?
- If nearly everyone is correct: ask what could go wrong at each step instead of going through them again.
Support
- Give the first and the last events already placed.
4. Following one request Explain 10 min
On the lesson window now
Purpose: A worked trace with DNS records, then independent trace questions, a corrected piece of faulty reasoning and a failure case.
Ask
- Which record applies, and why not the others?
- What is wrong with Noah's reasoning?
- At which step does a mistyped domain name fail?
Responses to expect
- The record whose name matches the whole domain name
- The browser needs the IP address before it can contact the web server
- The DNS lookup
Misconceptions to challenge
- A learner may believe: “The DNS record is chosen by its position in the list.” Respond: The whole domain name is matched: shop.example.com has its own record.
- A learner may believe: “A misspelt address reaches the web server, which then reports an error.” Respond: The lookup fails first: no record means no IP address and so no request.
Checking understanding: The three questions diagnose different things: matching, order of steps, and where a failure occurs.
Depending on the answers
- If learners choose the wrong record: underline the whole domain name typed and run a finger down the table to the exact match.
Stretch
- What do you think happens if the DNS server does not have a record at all?
In the lesson window
- Apply it: Priya types https://shop.example.com/offers/today.html. Using the records, to which IP address does her browser send the request for the page?
- Apply it: Noah says: “The browser asks the web server for the IP address, because the web server knows where the page is.” What is wrong with this?
- Apply it: A pupil mistypes the domain name as www.exmaple.org, and the browser shows “server not found”. Which step has failed?
5. A shop that forgets you Think 9 min
On the lesson window now
Purpose: Learners work out for themselves why a website needs a way to recognise a browser, before the term cookie is introduced, and then meet the four uses.
Ask
- How could the server tell that two requests come from the same browser?
- What does the cookie hold in the basket example?
Responses to expect
- Something carried with every request, like a cloakroom ticket
- A code that the server links to a basket
Misconceptions to challenge
- A learner may believe: “The website remembers because the computer is the same.” Respond: The server only sees requests. Without a cookie it cannot tell one browser from another.
- A learner may believe: “The cookie holds the whole basket.” Respond: In the design shown it holds a code; the shop's server keeps the basket. Other designs differ.
On the board or with the pen
- Draw browser and server with arrows for the cookie going to the browser and coming back with each later request.
Checking understanding: The preference question tests whether the four uses are understood and not merely listed.
Depending on the answers
- If learners cannot link a language setting to a cookie: ask what the site would have to do if the choice were forgotten every visit.
In the lesson window
- Think it through: How could the shop’s web server work out that the second request comes from the same browser as the first, so that it shows the same basket? Hint: what could the browser carry with it?
- Check your understanding: A video website remembers that a pupil chose subtitles in French, so subtitles are on next time. Which use of cookies is this?
6. How long should a cookie last? Discover 7 min
On the lesson window now
Purpose: Distinguish session and persistent cookies by the learners' own judgement about what should last, then sort scenarios.
Ask
- Which things should be forgotten when the browser closes, and which kept?
- Which kind of cookie has an expiry date?
Responses to expect
- Basket and bank login forgotten; language and theme kept
- Persistent
Misconceptions to challenge
- A learner may believe: “A session cookie lasts a fixed time, such as an hour.” Respond: A session cookie has no expiry date and ends when the browser is closed.
- A learner may believe: “Persistent cookies are stored on the server.” Respond: Both kinds are stored by the browser on the device.
On the board or with the pen
- Draw a timeline with 'browser closed' marked; show a session cookie ending there and a persistent cookie continuing to its expiry date.
Checking understanding: The classification table, then Jonas's claim: a learner who corrects Jonas correctly can state the difference without a prompt.
Depending on the answers
- If learners mix up the two kinds: ask what ends each one, and write 'browser closes' and 'expiry date' side by side.
In the lesson window
- Think it through: Fatima closes her browser. Should the basket still be full when she opens it tomorrow? Should the site still remember her language choice? Should her bank still keep her logged in? Give a reason for each.
- Apply it: Jonas says: “A session cookie is one that is deleted after an hour, and a persistent cookie never expires.” Which correction is right?
7. Cookies and privacy Explain 7 min
On the lesson window now
Purpose: Make privacy considerations concrete: a shared computer, tracking across sites, consent and control; and correct the belief that cookies are programs.
Ask
- What could go wrong if you tick 'keep me logged in' on a shared computer?
- What can a company that places cookies on many sites find out?
Responses to expect
- The next user could use the account
- Which sites the same browser visits, so a profile of interests
Misconceptions to challenge
- A learner may believe: “Cookies can carry viruses.” Respond: A cookie is text, not a program, so it cannot run. The concern is privacy.
- A learner may believe: “Cookies are illegal.” Respond: They are allowed. In the UK a site must ask permission for cookies it does not need to work.
Checking understanding: The advertising scenario: look for 'tracking' rather than 'virus' in learners' reasons.
Depending on the answers
- If learners suggest deleting all cookies as the answer: ask what they would lose: saved baskets and logins; it is a trade-off, and the choice is theirs.
English as an additional language
- Check 'consent': giving permission after being told what will happen.
In the lesson window
- Think it through: A pupil uses a library computer and ticks “keep me logged in” on a website. They walk away without logging out. What could go wrong, and which kind of cookie is involved?
- Apply it: A fictional news website sets cookies from an advertising company on every page. Which privacy concern is most directly raised?
8. Show what you know Consolidate 7 min
On the lesson window now
Purpose: Explain the whole journey, apply it to a failure, choose a cookie type with a reason, then the summary.
Ask
- Explain what happens from typing a URL to seeing the page, using the seven words.
- Why does the bank need a session cookie, not a persistent one?
Responses to expect
- The six events in order, with the right words
- A shared computer would otherwise stay logged in
Checking understanding: Use the explanations to check that DNS, the web server and rendering appear in the right order; the failed-page question checks the lookup.
Depending on the answers
- If explanations skip the DNS lookup: ask the learner what the browser holds after reading the URL, and what it needs next.
In the lesson window
- Think it through: Explain to a friend what happens from typing a URL to seeing the page. Use the words browser, domain name, DNS server, IP address, web server, HTML and render.
- Apply it: A pupil’s browser shows a page on one website with no trouble, but another website shows “server not found”, and its address is spelt correctly. Which explanation fits best?
- Apply it: An online bank wants a cookie to keep its customers logged in while they move around the site, but it must not stay on a shared computer after the window is closed. Which is the best choice, and why?
Lesson recap Closing
On the lesson window now
On screen: the lesson’s objectives again; Next adds the closing question, which asks the class to explain each one in their own words without looking back. It says nothing about what anyone has learnt: use the answers to decide what to revisit.
Points to listen for
- Browser reads the URL, asks the DNS server for the IP address, sends a request to the web server, receives the HTML and renders it.
- A DNS server links domain names to IP addresses; with no record, the lookup fails and no request is sent.
- A cookie is a small text file the browser stores and sends back, so a website can recognise it; uses are personal details, preferences, shopping carts and logins.
- A session cookie ends when the browser closes; a persistent cookie lasts until its expiry date; privacy depends on shared devices, tracking and consent.
Consolidation
- Browser reads the URL, asks the DNS server for the IP address, sends a request to the web server, receives the HTML and renders it.
- A DNS server links domain names to IP addresses; with no record, the lookup fails and no request is sent.
- A cookie is a small text file the browser stores and sends back, so a website can recognise it; uses are personal details, preferences, shopping carts and logins.
- A session cookie ends when the browser closes; a persistent cookie lasts until its expiry date; privacy depends on shared devices, tracking and consent.