Solice UI
Back to the curriculum

Chapter 1 · How the Web Works

Request-response lifecycle

A page load feels immediate, but it is a sequence of small jobs. Knowing the sequence makes loading problems easier to locate without memorizing every networking detail.

Beginner · Lesson 4 of 6 in this chapter

Connection comes before content

The browser resolves the domain, establishes a secure connection, and sends the request. Reused connections and cached answers can shorten these steps on later visits.

The response can lead elsewhere

A successful response can return the document, but a redirect asks the browser to request another address. An error status explains that the resource was missing, access was denied, or the server could not complete the work.

Following an old bookmark

  1. The browser requests the saved address.
  2. The server redirects it because the page moved.
  3. The browser requests the new address and receives the current document.
  • A page load has ordered network steps.
  • Redirects create another request instead of returning the final page.
  • Status codes describe outcomes; they are not the page content itself.