Still loading. This can take a moment on a slow connection.
Still loading. This can take a moment on a slow connection.
Follow a web address from the browser to the page, through the DNS and the web server, and say what the client and the server each do.
URLThe browser reads the URL https://conceptorbit.example/courses: the protocol is https, the domain name is conceptorbit.example, and the path to the page is /courses.
Browserthe client▶ Working
The browser is reading the URL.
DNS serverWaiting
Finds the IP address for a domain name.
Web serverWaiting
Holds the pages. Its IP address is not known yet.
At the DNS, the connection, the web server and the page’s script, say what will happen before you step on. Play waits for you.
After your first prediction, this says why it works.
Try what you found on the lesson’s 44 marked questions. Practise in IP Addresses and Routers
Break a stage
Each acts on the site in the URL. The run starts again.
Key
Beyond the syllabus Status codes, and the split between processing on the server and processing in the browser, go beyond the 0478 syllabus; the course’s Web applications lesson teaches them. So do the names of the DNS servers a lookup passes through, which the lab leaves out.
This internet is small. conceptorbit.example and library.example are its own sites; any other domain name with a real top-level domain gets a made-up web server that has every page asked for, at an IP address from the ranges kept for examples. A real browser also fetches the images, style sheets and scripts a page names, each with a request of its own.