GET route handling in Express - Step-by-Step Execution

Concept Flow - GET route handling

Client sends GET request

↓

Express server receives request

↓

Match request URL to route handler

Yes↓

Execute route handler function

↓

Send response back to client

↓

End

This flow shows how Express handles a GET request: client sends request, server matches route, runs handler, and sends response.

Execution Sample

Express

const express = require('express');
const app = express();
app.get('/hello', (req, res) => {
  res.send('Hello World!');
});
app.listen(3000);

This code sets up an Express server that responds with 'Hello World!' when a GET request is made to '/hello'.

Execution Table

Step	Action	Request URL	Route Matched	Handler Executed	Response Sent
1	Client sends GET request	/hello	No	No	No
2	Server receives request	/hello	No	No	No
3	Check route '/hello'	/hello	Yes	No	No
4	Execute handler for '/hello'	/hello	Yes	Yes	No
5	Send response 'Hello World!'	/hello	Yes	Yes	Yes
6	Request complete	/hello	Yes	Yes	Yes

💡 Request completes after response is sent to client.

Variable Tracker

Variable	Start	After Step 1	After Step 3	After Step 4	Final
request.url	undefined	/hello	/hello	/hello	/hello
routeMatched	false	false	true	true	true
handlerExecuted	false	false	false	true	true
responseSent	false	false	false	false	true

Key Moments - 2 Insights

Why does the server only execute the handler when the route matches?

Because Express checks the request URL against defined routes (see Step 3 in execution_table). If it doesn't match, the handler won't run.

What happens if the response is not sent in the handler?

The client will wait indefinitely because the server never completes the request (see Step 5 where responseSent changes to true).

Visual Quiz - 3 Questions

Look at the execution table, at which step does the route get matched?

A Step 3

B Step 2

C Step 4

D Step 5

💡 Hint

Check the 'Route Matched' column in the execution_table.

According to variable_tracker, what is the value of 'handlerExecuted' after Step 3?

A true

B false

C undefined

D null

💡 Hint

Look at the 'handlerExecuted' row and the 'After Step 3' column.

If the client sends a GET request to '/bye', what would happen in the execution table?

A Response sent immediately without handler

B Route Matched would be 'Yes' and handler executed

C Route Matched would be 'No' and handler not executed

D Server crashes

💡 Hint

Routes only match exact paths defined in Express (see Step 3).

Concept Snapshot

GET route handling in Express:
- Use app.get(path, handler) to define a GET route
- When a client requests that path, Express runs the handler
- Handler receives request and response objects
- Use res.send() to send response back
- Server listens on a port to accept requests

Full Transcript

This visual execution shows how Express handles a GET request. First, the client sends a GET request to the server. The server receives it and checks if the URL matches any defined GET routes. If it matches, Express runs the route handler function. The handler sends a response back to the client, completing the request. Variables like request.url, routeMatched, handlerExecuted, and responseSent change step-by-step to track progress. Key moments include understanding route matching and the importance of sending a response. The quiz tests knowledge of these steps and variable states.