Why middleware processes requests before handlers in NestJS - Quick Recap

Recall & Review

beginner

What is the main role of middleware in NestJS?

Middleware in NestJS runs before request handlers to process or modify requests, like checking authentication or logging, before the main handler runs.

beginner

Why does middleware run before route handlers in NestJS?

Middleware runs first to prepare or validate the request, so handlers receive clean, checked data and can focus on business logic.

intermediate

How does middleware improve code organization in NestJS?

Middleware separates common tasks like logging or authentication from handlers, keeping handlers simple and focused on their main job.

intermediate

Can middleware stop a request from reaching the handler in NestJS? How?

Yes, middleware can end the request early by sending a response or throwing an error, preventing the handler from running if conditions aren’t met.

beginner

Give an example of a task middleware might do before a handler runs.

Middleware might check if a user is logged in and has permission before letting the request reach the handler.

Why does middleware run before request handlers in NestJS?

A To prepare or validate the request before the handler processes it

B To run after the handler finishes processing

C To replace the handler completely

D To handle database connections only

Middleware runs before handlers to prepare or validate requests, ensuring handlers get clean data.

What can middleware do if a request is invalid?

A Modify the request and continue

B Stop the request by sending a response or error

C Ignore the request and do nothing

D Automatically fix the request data

Middleware can stop the request early by sending a response or error if validation fails.

Which of these is a common use of middleware in NestJS?

A Checking user authentication

B Writing database queries

C Rendering HTML templates

D Defining API routes

Middleware often checks user authentication before handlers run.

How does middleware help keep route handlers simple?

A By writing all business logic inside middleware

B By replacing the need for controllers

C By handling common tasks like logging and validation separately

D By delaying request processing

Middleware handles common tasks so handlers focus on main business logic.

In NestJS, when is middleware executed?

A Only on server startup

B After the route handler finishes

C Only on errors

D Before the route handler runs

Middleware runs before route handlers to process requests first.

Explain why middleware processes requests before handlers in NestJS and how this benefits the application.

Think about how middleware acts like a gatekeeper before the main work.

Describe a real-life example where middleware processing before handlers is useful in a NestJS app.

Imagine a security guard checking IDs before letting people enter a building.

Practice

1. Why does middleware in NestJS process requests before the route handlers?

easy

A. To delay the request processing intentionally

B. To send the response after the handler finishes

C. To replace the route handler completely

D. To prepare or check the request before the handler uses it

Solution

1. Step 1: Understand middleware role

   Middleware runs before handlers to prepare or validate requests, like checking authentication or adding data.

2. Step 2: Compare with other options

   Middleware does not send responses after handlers or replace handlers; it only processes requests early.

3. Final Answer:

   To prepare or check the request before the handler uses it -> Option D

4. Quick Check:

   Middleware prepares requests = D [OK]

Hint: Middleware runs first to prep requests before handlers [OK]

Common Mistakes:

• Thinking middleware runs after handlers
• Believing middleware replaces handlers
• Assuming middleware delays requests

2. Which of the following is the correct way to continue request processing inside a NestJS middleware?

easy

A. Return the response directly

B. Call next() function

C. Throw an error to stop processing

D. Call the route handler manually

Solution

1. Step 1: Identify middleware flow control

   In NestJS, calling next() passes control to the next middleware or handler.

2. Step 2: Eliminate incorrect options

   Returning response or throwing error stops flow; calling handler manually is not standard.

3. Final Answer:

   Call next() function -> Option B

4. Quick Check:

   Use next() to continue middleware chain [OK]

Hint: Always call next() to move forward in middleware [OK]

Common Mistakes:

• Forgetting to call next(), causing request hang
• Trying to call handler directly inside middleware
• Returning response without next() when not ending request

3. Given this NestJS middleware code snippet, what will be logged first when a request arrives?

export function logger(req, res, next) {
  console.log('Middleware start');
  next();
  console.log('Middleware end');
}

medium

A. "Middleware start" then "Middleware end"

B. "Middleware end" then "Middleware start"

C. Only "Middleware start" is logged

D. No logs appear because next() stops execution

Solution

1. Step 1: Analyze middleware execution order

   Console logs before and after next() run synchronously; first logs "Middleware start".

2. Step 2: Understand next() behavior

   Calling next() passes control but does not pause middleware; "Middleware end" logs after next() call.

3. Final Answer:

   "Middleware start" then "Middleware end" -> Option A

4. Quick Check:

   Logs before and after next() run in order [OK]

Hint: Logs before and after next() run in sequence [OK]

Common Mistakes:

• Thinking next() pauses middleware execution
• Assuming logs after next() run later
• Believing next() stops middleware code

4. You wrote this NestJS middleware but requests never reach the handler. What is the problem?

export function authMiddleware(req, res, next) {
  if (!req.headers.authorization) {
    res.status(401).send('Unauthorized');
    return;
  }
  next();
}

medium

A. Middleware must not send responses directly

B. Authorization header check is incorrect syntax

C. next() is called even after sending response, causing errors

D. next() should be called before checking headers

Solution

1. Step 1: Review middleware flow control

   If authorization header is missing, response is sent but next() is still called, causing request to continue incorrectly.

2. Step 2: Fix flow by returning early

   To stop processing after sending response, return immediately without calling next().

3. Final Answer:

   next() is called even after sending response, causing errors -> Option C

4. Quick Check:

   Don't call next() after sending response [OK]

Hint: Return after sending response to avoid calling next() [OK]

Common Mistakes:

• Calling next() after response ends
• Not returning early to stop middleware
• Misunderstanding middleware flow control

5. You want to add a middleware that adds a timestamp to every request before handlers run. Which approach correctly ensures the timestamp is available in the handler?

hard

A. Add req.timestamp = Date.now() in middleware, then call next()

B. Call next() first, then add req.timestamp after

C. Add timestamp in the handler, not middleware

D. Send timestamp in response headers from middleware

Solution

1. Step 1: Understand middleware purpose

   Middleware runs before handlers, so adding data to req here makes it available later.

2. Step 2: Correct order of operations

   Assign req.timestamp before calling next() so handlers see the value.

3. Final Answer:

   Add req.timestamp = Date.now() in middleware, then call next() -> Option A

4. Quick Check:

   Add data before next() to share with handlers [OK]

Hint: Set request data before next() to share with handlers [OK]

Common Mistakes:

• Adding data after next(), so handlers miss it
• Trying to add data in handlers instead of middleware
• Sending data only in response headers