0
0
Intro to Computingfundamentals~6 mins

How web browsers request pages in Intro to Computing - Step-by-Step Explanation

Choose your learning style9 modes available
Introduction
Imagine you want to read an article online, but you need a way to get that article from a website to your screen. Web browsers solve this by sending requests to websites and then showing you the pages they send back.
Explanation
User enters a URL
The process starts when you type a website address, called a URL, into the browser's address bar. This tells the browser exactly which page you want to see.
The URL tells the browser where to find the page you want.
Browser sends a request
The browser sends a message called an HTTP request over the internet to the website's server. This request asks the server to send the page you want.
The browser asks the website's server for the page using an HTTP request.
Server processes the request
The website's server receives the request and looks for the page you asked for. It then prepares the page data to send back to your browser.
The server finds and prepares the requested page to send back.
Browser receives the response
The server sends the page data back to your browser in a message called an HTTP response. This response contains the content of the page.
The browser gets the page content from the server's response.
Browser displays the page
Finally, the browser reads the page data and shows it on your screen so you can read or interact with it.
The browser turns the received data into the visible web page.
Real World Analogy

Imagine you want to read a book from a library. You tell the librarian the book's title (URL). The librarian goes to find the book (server processes request), then brings it back to you (server sends response). You then open the book and read it (browser displays page).

User enters a URL → Telling the librarian the book's title you want
Browser sends a request → The librarian going to find the book in the library
Server processes the request → The librarian locating and picking the book from the shelf
Browser receives the response → The librarian bringing the book back to you
Browser displays the page → You opening and reading the book
Diagram
Diagram
┌───────────────┐       HTTP Request       ┌───────────────┐
│   Browser     │─────────────────────────▶│    Server     │
│ (Your device) │                         │ (Website host)│
└───────────────┘                         └───────────────┘
        ▲                                         │
        │             HTTP Response               │
        └─────────────────────────────────────────┘
                 
       Browser displays the page on screen
This diagram shows the browser sending a request to the server and receiving a response, then displaying the page.
Key Facts
URLA web address that tells the browser which page to request.
HTTP RequestA message sent by the browser asking the server for a web page.
ServerA computer that stores websites and sends pages when requested.
HTTP ResponseThe message from the server containing the requested web page.
BrowserSoftware that requests, receives, and shows web pages to users.
Common Confusions
Thinking the browser stores the web page permanently.
Thinking the browser stores the web page permanently. The browser only temporarily holds the page data; the original page stays on the server.
Believing the server sends the page automatically without a request.
Believing the server sends the page automatically without a request. The server only sends pages after the browser asks for them with a request.
Summary
Web browsers get web pages by sending requests to servers and showing the responses.
A URL tells the browser which page to ask for from the server.
The server sends the page data back, and the browser displays it on your screen.