Bird
Raised Fist0
Intro to Computingfundamentals~10 mins

How web browsers request pages in Intro to Computing - Draw the Process

Choose your learning style10 modes available
LearnWhyDeepFlowTryChallengeDrawRecallReal

Start learning this pattern below

Jump into concepts and practice - no test required

or
Recommended
Test this pattern10 questions across easy, medium, and hard to know if this pattern is strong
Draw This - beginner

Draw a flowchart that shows the steps a web browser takes to request and receive a web page from a server.

10 minutes
Hint 1
Hint 2
Hint 3
Hint 4
Grading Criteria
Start and End symbols present
Flowchart shows user action as start
Browser sending request step included
Server receiving and processing request shown
Server sending response step included
Browser receiving response step included
Browser displaying page step included
Arrows correctly show flow direction
Solution
  +-------------------+
  | Start: User action |
  +---------+---------+
            |
            v
  +-------------------+
  | Browser sends HTTP|
  | request to server |
  +---------+---------+
            |
            v
  +-------------------+
  | Server receives   |
  | request           |
  +---------+---------+
            |
            v
  +-------------------+
  | Server processes  |
  | request and sends |
  | HTTP response     |
  +---------+---------+
            |
            v
  +-------------------+
  | Browser receives  |
  | response          |
  +---------+---------+
            |
            v
  +-------------------+
  | Browser displays  |
  | the web page      |
  +---------+---------+
            |
            v
  +-------------------+
  | End               |
  +-------------------+

This flowchart shows the simple steps a web browser follows to get a web page:

  1. User action: The user types a web address (URL) or clicks a link.
  2. Browser sends request: The browser sends an HTTP request to the web server that hosts the page.
  3. Server receives request: The server gets the request and understands what page is needed.
  4. Server processes and responds: The server prepares the web page and sends it back as an HTTP response.
  5. Browser receives response: The browser gets the page data from the server.
  6. Browser displays page: The browser shows the web page to the user.

This process happens very fast, so the user sees the page almost immediately.

Variations - 2 Challenges
[intermediate] Draw a flowchart showing how a web browser requests a web page and handles a '404 Not Found' error from the server.
[advanced] Draw a detailed flowchart illustrating how a web browser requests a web page, including DNS lookup, establishing a connection, sending the request, receiving the response, and rendering the page.

Practice

(1/5)
1. What does a web browser send to a server when you type a website address and press Enter?
easy
A. A file containing the webpage
B. A command to shut down the server
C. A request asking for the webpage
D. A message to update the browser

Solution

  1. Step 1: Understand browser-server interaction

    When you enter a website address, the browser needs to get the page from the server.

  2. Step 2: Identify what the browser sends

    The browser sends a request to the server asking for the webpage data.

  3. Final Answer:

    A request asking for the webpage -> Option C

  4. Quick Check:

    Browser sends request [OK]
Hint: Browser always sends a request to get pages [OK]
Common Mistakes:
  • Thinking browser sends the whole page first
  • Confusing request with response
  • Assuming browser sends commands to server
2. Which protocol do web browsers use to request pages from servers?
easy
A. HTTP or HTTPS
B. FTP
C. SMTP
D. POP3

Solution

  1. Step 1: Recall common internet protocols

    FTP is for file transfer, SMTP and POP3 are for email.

  2. Step 2: Identify protocols for web pages

    HTTP and HTTPS are designed for web page requests and responses.

  3. Final Answer:

    HTTP or HTTPS -> Option A

  4. Quick Check:

    Web pages use HTTP/HTTPS [OK]
Hint: Web pages use HTTP or HTTPS protocols [OK]
Common Mistakes:
  • Confusing FTP with HTTP
  • Mixing email protocols with web protocols
  • Not recognizing HTTPS as secure HTTP
3. Look at this simplified flowchart of a browser requesting a page: 1. Browser sends request to server 2. Server checks if page exists 3. Server sends page if found, else sends error If the server does not find the page, what will the browser receive?
medium
A. An error message like 404 Not Found
B. A blank page with no message
C. The requested webpage content
D. A request to try again

Solution

  1. Step 1: Follow the flowchart steps

    The server checks if the page exists after receiving the request.

  2. Step 2: Understand server response if page missing

    If the page is missing, the server sends an error message like 404 Not Found.

  3. Final Answer:

    An error message like 404 Not Found -> Option A

  4. Quick Check:

    Missing page = error 404 message [OK]
Hint: Missing pages return 404 error messages [OK]
Common Mistakes:
  • Assuming server sends blank page
  • Thinking server asks browser to retry
  • Confusing error with page content
4. A browser sends a request to a server but the page never loads. Which of these could be the problem?
medium
A. The user typed the address in uppercase letters
B. The browser sent the wrong page address
C. The browser is using HTTP instead of HTTPS
D. The server is offline or unreachable

Solution

  1. Step 1: Analyze possible causes for no page load

    If the server is offline or unreachable, the browser cannot get any response.

  2. Step 2: Evaluate other options

    Wrong address usually returns error, HTTP vs HTTPS usually still connects, uppercase letters do not prevent loading.

  3. Final Answer:

    The server is offline or unreachable -> Option D

  4. Quick Check:

    No response = server offline/unreachable [OK]
Hint: No page load often means server unreachable [OK]
Common Mistakes:
  • Thinking uppercase letters break address
  • Confusing HTTP and HTTPS connection issues
  • Assuming wrong address causes no load instead of error
5. You want to explain how a browser requests a webpage and gets a response using a simple diagram. Which sequence correctly shows the steps?
hard
A. Server sends response -> Browser sends request -> Server processes response -> Browser displays page
B. Browser sends request -> Server processes request -> Server sends response -> Browser displays page
C. Browser sends response -> Server sends request -> Browser processes response -> Server displays page
D. Server sends request -> Browser processes request -> Browser sends response -> Server displays page

Solution

  1. Step 1: Understand the communication flow

    The browser initiates by sending a request to the server.

  2. Step 2: Follow the correct order of actions

    The server processes the request, sends back a response, and then the browser displays the page.

  3. Final Answer:

    Browser sends request -> Server processes request -> Server sends response -> Browser displays page -> Option B

  4. Quick Check:

    Request -> Process -> Response -> Display [OK]
Hint: Request starts at browser, response ends at browser [OK]
Common Mistakes:
  • Reversing who sends request or response
  • Mixing up processing and displaying steps
  • Thinking server displays page