app.all and app.use for catch-all in Express - Step-by-Step Execution

Concept Flow - app.all and app.use for catch-all

Incoming HTTP Request

↓

app.all('/path', handler)

↓

app.use(handler)

↓

Handler executes or passes to next middleware

↓

Response sent or 404 if no match

Requests first check app.all for specific paths and all methods, then app.use catches any unmatched requests as a fallback.

Execution Sample

Express

app.all('/test', (req, res) => {
  res.send('Handled by app.all');
});

app.use((req, res) => {
  res.status(404).send('Catch-all 404');
});

This code handles all HTTP methods on '/test' with app.all, and uses app.use as a catch-all for any other requests.

Execution Table

Step	Request Method	Request Path	Matched Middleware	Action Taken	Response Sent
1	GET	/test	app.all('/test')	Handler runs, sends 'Handled by app.all'	'Handled by app.all'
2	POST	/test	app.all('/test')	Handler runs, sends 'Handled by app.all'	'Handled by app.all'
3	GET	/unknown	app.all('/test')	No match, pass to next	No response yet
4	GET	/unknown	app.use (catch-all)	Handler runs, sends 404 message	'Catch-all 404'

💡 Requests not matching app.all path fall through to app.use catch-all middleware which sends 404.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
req.path	/test	/test	/test	/unknown	/unknown
req.method	GET	GET	POST	GET	GET
responseSent	false	true	true	false	true

Key Moments - 2 Insights

Why does app.all handle both GET and POST requests on the same path?

app.all matches all HTTP methods for the specified path, so both GET and POST requests to '/test' trigger the same handler as shown in steps 1 and 2.

What happens when a request path does not match app.all?

The request passes to the next middleware, here app.use, which acts as a catch-all and handles unmatched requests by sending a 404 response, as seen in steps 3 and 4.

Visual Quiz - 3 Questions

Look at the execution table, what response is sent for a POST request to '/test'?

A 'Catch-all 404'

B 'Handled by app.all'

C No response sent

D Error

💡 Hint

Check row 2 in the execution table where POST '/test' is handled by app.all.

At which step does the catch-all middleware send a response?

A Step 1

B Step 3

C Step 4

D Step 2

💡 Hint

Look at the execution table row 4 where app.use sends the 404 response.

If app.all was removed, what would happen to a GET request to '/test'?

A It would be handled by app.use catch-all sending 404

B It would send 'Handled by app.all'

C No response would be sent

D Server would crash

💡 Hint

Refer to variable_tracker and execution_table showing app.use handles unmatched paths.

Concept Snapshot

app.all(path, handler) matches all HTTP methods for a specific path.
app.use(handler) matches all paths and methods, often used as catch-all.
Requests first try app.all, then fall through to app.use if no match.
Use app.use last to handle 404 or fallback responses.
Handlers send responses or call next() to pass control.

Full Transcript

This visual execution trace shows how Express.js uses app.all and app.use for catch-all routing. When a request comes in, app.all matches all HTTP methods for a specific path, handling requests like GET or POST to '/test'. If the request path does not match app.all, the request passes to app.use, which acts as a catch-all middleware to handle any unmatched requests, often sending a 404 response. The execution table tracks requests step-by-step, showing which middleware matches and what response is sent. Variable tracking shows request path, method, and response status changing over steps. Key moments clarify why app.all handles all methods and how app.use catches unmatched routes. The quiz tests understanding of which middleware handles which requests and what responses are sent. The snapshot summarizes usage rules for app.all and app.use in Express routing.

Practice

1. What does app.all('/path', handler) do in an Express app?

easy

A. It handles all HTTP methods for the specific '/path' route.

B. It adds middleware for all routes starting with '/path'.

C. It only handles GET requests for '/path'.

D. It handles all routes and methods globally.

Solution

1. Step 1: Understand app.all usage

   app.all is designed to handle every HTTP method (GET, POST, PUT, DELETE, etc.) but only for the exact route specified.

2. Step 2: Compare with other methods

   app.use adds middleware for all methods but for routes starting with a prefix, not just one exact path.

3. Final Answer:

   It handles all HTTP methods for the specific '/path' route. -> Option A

4. Quick Check:

   app.all = all methods, exact path [OK]

Hint: Remember: app.all = all methods, one exact path [OK]

Common Mistakes:

• Confusing app.all with app.use
• Thinking app.all handles all routes globally
• Assuming app.all only handles GET requests

2. Which of the following is the correct syntax to add a catch-all middleware for all routes in Express without specifying a path?

easy

A. app.all('*', (req, res) => { res.send('Catch all'); });

B. app.use((req, res) => { res.send('Catch all'); });

C. app.use('*', (req, res) => { res.send('Catch all'); });

D. app.all((req, res) => { res.send('Catch all'); });

Solution

1. Step 1: Understand catch-all middleware syntax

   Using app.use without a path applies middleware to all routes and methods.

2. Step 2: Analyze options

   app.all('*', (req, res) => { res.send('Catch all'); }); and app.use('*', (req, res) => { res.send('Catch all'); }); both specify a path '*'. app.all((req, res) => { res.send('Catch all'); }); is invalid syntax.

3. Final Answer:

   app.use((req, res) => { res.send('Catch all'); }); -> Option B

4. Quick Check:

   app.use without path = catch-all middleware [OK]

Hint: app.use without path catches all routes and methods [OK]

Common Mistakes:

• Using app.use('*', ...) which specifies a path
• Using app.all without a path argument
• Confusing app.all and app.use syntax

3. What will be the output when a GET request is made to '/test' in this Express app?

const express = require('express');
const app = express();

app.all('/test', (req, res, next) => {
  res.write('all ');
  next();
});

app.use('/test', (req, res) => {
  res.end('use');
});

app.listen(3000);

medium

A. Error: Cannot set headers after they are sent

B. use

C. all use

D. all

Solution

1. Step 1: Trace app.all handler

   For GET '/test', app.all('/test') runs first, writes 'all ' to response, then calls next() to continue.

2. Step 2: Trace app.use handler

   Next, app.use('/test') matches and ends the response with 'use'. So the full response is 'all use'.

3. Final Answer:

   all use -> Option C

4. Quick Check:

   app.all writes + next() then app.use ends response [OK]

Hint: app.all runs first, next() continues to app.use [OK]

Common Mistakes:

• Assuming app.use runs before app.all
• Thinking res.end in app.use causes error here
• Ignoring next() call in app.all

4. Identify the error in this Express code snippet:

app.all('/api', (req, res) => {
  res.send('API all methods');
  next();
});

medium

A. Calling next() after res.send() causes an error.

B. app.all cannot be used with '/api' path.

C. res.send() must be called twice in app.all.

D. No error, code works fine.

Solution

1. Step 1: Understand res.send() behavior

   res.send() ends the response and sends data to client.

2. Step 2: Analyze next() call after res.send()

   Calling next() after res.send() tries to continue middleware chain after response ended, causing an error.

3. Final Answer:

   Calling next() after res.send() causes an error. -> Option A

4. Quick Check:

   res.send ends response; next() after it is wrong [OK]

Hint: Never call next() after res.send() or res.end() [OK]

Common Mistakes:

• Thinking next() is always safe after res.send()
• Believing app.all can't use paths
• Ignoring response end behavior

5. You want to create a global catch-all middleware without specifying a path that logs every request method and URL, then passes control to the next handler. Which code correctly implements this in Express?

hard

A. app.all('*', (req, res, next) => { console.log(req.method, req.url); next(); });

B. app.all((req, res, next) => { console.log(req.method, req.url); next(); });

C. app.use('*', (req, res, next) => { console.log(req.method, req.url); next(); });

D. app.use((req, res, next) => { console.log(req.method, req.url); next(); });

Solution

1. Step 1: Understand global middleware with app.use

   Using app.use without a path applies middleware to all routes and methods globally.

2. Step 2: Analyze options for logging middleware

   app.all('*', (req, res, next) => { console.log(req.method, req.url); next(); }); and app.use('*', (req, res, next) => { console.log(req.method, req.url); next(); }); specify a path '*'. app.all((req, res, next) => { console.log(req.method, req.url); next(); }); is invalid syntax.

3. Final Answer:

   app.use((req, res, next) => { console.log(req.method, req.url); next(); }); -> Option D

4. Quick Check:

   app.use without path = global middleware [OK]

Hint: Use app.use without path for global middleware [OK]

Common Mistakes:

• Using app.use('*', ...) which specifies a path
• Using app.all without path argument
• Forgetting to call next() in middleware