Why understanding req matters in Express - Challenge Your Understanding

Challenge - 5 Problems

❓ component_behavior

intermediate

What does this Express route output when receiving a GET request with query ?name=Alex?

Consider this Express route handler. What will the response be if the client sends a GET request to /hello?name=Alex?

Express

app.get('/hello', (req, res) => {
  res.send(`Hello, ${req.query.name}!`);
});

A Error: req.query is not defined

B Hello, Alex!

C Hello, !

D Hello, undefined!

💡 Hint

Look at how req.query accesses URL query parameters.

The req.query object contains the parsed query string parameters. Here, req.query.name is 'Alex', so the response is 'Hello, Alex!'.

❓ state_output

intermediate

What is the value of req.params.id in this route for URL /user/42?

Given this Express route, what will be the value of req.params.id when a client requests /user/42?

Express

app.get('/user/:id', (req, res) => {
  res.send(`User ID is ${req.params.id}`);
});

A User ID is 42

B User ID is :id

C User ID is undefined

D User ID is /user/42

💡 Hint

Check how route parameters are accessed via req.params.

The :id in the route path captures the segment after /user/. For /user/42, req.params.id is '42'.

📝 Syntax

advanced

Which option correctly accesses JSON data sent in a POST request body?

Assuming Express is set up with express.json() middleware, which code correctly reads the 'username' field from the request body?

Express

app.post('/login', (req, res) => {
  // Access username here
});

A const user = req.query.username;

B const user = req.params.username;

C const user = req.body.username;

D const user = req.headers.username;

💡 Hint

Where does Express store parsed JSON data from the request body?

The req.body object contains parsed data from the request body when using express.json() middleware. req.params and req.query are for URL parameters and query strings, headers are different.

🔧 Debug

advanced

Why does this Express route always respond with 'undefined' for req.body.name?

Look at this code snippet. Why does req.body.name print 'undefined' even when the client sends JSON with a 'name' field?

Express

app.post('/submit', (req, res) => {
  console.log(req.body.name);
  res.send('Received');
});

A req.body.name is always undefined in POST requests.

B The route path is incorrect, so req.body is empty.

C The client did not send a 'name' field in the JSON body.

D The express.json() middleware is missing, so req.body is undefined.

💡 Hint

Check if the server can parse JSON bodies.

Without express.json() middleware, Express does not parse JSON request bodies, so req.body remains undefined.

🧠 Conceptual

expert

Why is understanding the req object crucial for building secure Express apps?

Which statement best explains why knowing the structure and content of the req object is important for security?

A Because req contains user input that must be validated to prevent attacks like injection or XSS.

B Because req automatically blocks all malicious requests without developer intervention.

C Because req only holds server configuration data, so it is unrelated to security.

D Because req is only used for logging and does not affect app behavior.

💡 Hint

Think about where user data comes from in Express apps.

The req object holds all data sent by the client, including user input. Validating and sanitizing this data is essential to protect the app from security threats.

Practice

1. In Express, what does the req object represent?

easy

A. Information sent by the user to the server

B. The server's response to the user

C. A database connection

D. A middleware function

Solution

1. Step 1: Understand the role of req in Express

   The req object contains all the information sent by the user to the server, such as URL parameters, query strings, and request body.

2. Step 2: Differentiate req from other objects

   The server's response is handled by res, not req. Database connections and middleware are separate concepts.

3. Final Answer:

   Information sent by the user to the server -> Option A

4. Quick Check:

   req = user info [OK]

Hint: Remember: req = request from user [OK]

Common Mistakes:

• Confusing req with res (response)
• Thinking req is a database connection
• Mixing req with middleware functions

2. Which of the following is the correct way to access URL parameters in Express?

easy

A. req.body.params

B. req.params

C. req.query.params

D. req.url.params

Solution

1. Step 1: Recall how Express stores URL parameters

   Express stores URL parameters in req.params, which holds key-value pairs from the route.

2. Step 2: Check other options for correctness

   req.body holds POST data, req.query holds query strings, and req.url is a string, not an object with params.

3. Final Answer:

   req.params -> Option B

4. Quick Check:

   URL params = req.params [OK]

Hint: URL params are always in req.params [OK]

Common Mistakes:

• Using req.body to get URL params
• Confusing query strings with URL params
• Trying to access params from req.url string

3. What will be logged by this Express route handler?

app.get('/user/:id', (req, res) => {
  console.log(req.query.name);
  res.send('Done');
});
// Request URL: /user/123?name=Alice

medium

A. undefined

B. 123

C. Alice

D. Error

Solution

1. Step 1: Identify what req.query.name accesses

   req.query holds query string parameters from the URL, so req.query.name gets the value of the 'name' query parameter.

2. Step 2: Match the request URL query

   The URL has ?name=Alice, so req.query.name is 'Alice'.

3. Final Answer:

   Alice -> Option C

4. Quick Check:

   Query param 'name' = Alice [OK]

Hint: Query strings are in req.query [OK]

Common Mistakes:

• Confusing req.params with req.query
• Expecting URL param instead of query param
• Assuming req.query is undefined if not in route

4. Identify the error in this Express route handler:

app.post('/submit', (req, res) => {
  const data = req.query.body;
  res.send(data);
});

medium

A. Using req.query instead of req.body to access POST data

B. Missing res.end() after res.send()

C. Route should be app.get, not app.post

D. req.body is not available without middleware

Solution

1. Step 1: Check how POST data is accessed

   POST data is sent in the request body and accessed via req.body, not req.query.

2. Step 2: Identify the mistake in the code

   The code incorrectly tries to get POST data from req.query.body, which is wrong; it should be req.body.

3. Final Answer:

   Using req.query instead of req.body to access POST data -> Option A

4. Quick Check:

   POST data = req.body, not req.query [OK]

Hint: POST data is in req.body, not req.query [OK]

Common Mistakes:

• Accessing POST data from req.query
• Forgetting to use body-parser middleware
• Confusing HTTP methods and data locations

5. You want to create an Express route that responds differently based on a URL parameter type and a query parameter sort. Which code correctly accesses both parameters?

hard

A. app.get('/items/:type', (req, res) => { const t = req.body.type; const s = req.body.sort; res.send(`${t} sorted by ${s}`); });

B. app.get('/items/:type', (req, res) => { const t = req.query.type; const s = req.params.sort; res.send(`${t} sorted by ${s}`); });

C. app.get('/items', (req, res) => { const t = req.params.type; const s = req.query.sort; res.send(`${t} sorted by ${s}`); });

D. app.get('/items/:type', (req, res) => { const t = req.params.type; const s = req.query.sort; res.send(`${t} sorted by ${s}`); });

Solution

1. Step 1: Identify where URL and query parameters are stored

   URL parameters like type are in req.params, and query parameters like sort are in req.query.

2. Step 2: Check each option for correct usage

   app.get('/items/:type', (req, res) => { const t = req.params.type; const s = req.query.sort; res.send(`${t} sorted by ${s}`); }); correctly uses req.params.type and req.query.sort. app.get('/items/:type', (req, res) => { const t = req.query.type; const s = req.params.sort; res.send(`${t} sorted by ${s}`); }); swaps them incorrectly. app.get('/items', (req, res) => { const t = req.params.type; const s = req.query.sort; res.send(`${t} sorted by ${s}`); }); misses the URL param in route. app.get('/items/:type', (req, res) => { const t = req.body.type; const s = req.body.sort; res.send(`${t} sorted by ${s}`); }); wrongly uses req.body which is for POST data.

3. Final Answer:

   req.params.type and req.query.sort -> Option D

4. Quick Check:

   URL param = req.params, query param = req.query [OK]

Hint: URL params in req.params, query params in req.query [OK]

Common Mistakes:

• Swapping req.params and req.query
• Missing URL param in route path
• Using req.body for GET parameters