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.