app.all and app.use for catch-all in Express - Mini Project: Build & Apply

Using app.all and app.use for Catch-All Routes in Express

📖 Scenario: You are building a simple Express web server that handles specific routes and also needs to catch any requests that do not match those routes.This is like having a receptionist who directs visitors to specific rooms but also has a default message for anyone who comes to the wrong door.

🎯 Goal: Create an Express server that responds to a specific route and uses app.all and app.use to catch all other requests and handle errors gracefully.

📋 What You'll Learn

Create an Express app instance

Use app.all to catch all HTTP methods on a specific path

Use app.use as a catch-all middleware for unmatched routes

Send appropriate responses for matched and unmatched routes

💡 Why This Matters

🌍 Real World

Web servers often need to handle many types of requests and provide default responses for unknown routes, improving user experience and debugging.

💼 Career

Understanding how to use Express routing and middleware is essential for backend web development jobs using Node.js.

1

Set up Express app and a specific route

Create an Express app by requiring express and calling express(). Then create a route handler for GET requests on '/hello' that sends the text 'Hello World!'.

Express

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

// Your code here

Hint

Use require('express') to import Express and express() to create the app. Then use app.get('/hello', ...) to handle GET requests.

2

Add a catch-all route using app.all

Add a route handler using app.all for the path '/all' that sends the text 'This handles all HTTP methods on /all'.

Express

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

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

// Your code here

Hint

Use app.all('/all', (req, res) => { ... }) to catch all HTTP methods on the /all path.

3

Add a catch-all middleware using app.use

Add a middleware using app.use that catches all requests not matched by previous routes and sends the text '404 Not Found' with status code 404.

Express

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

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

app.all('/all', (req, res) => {
  res.send('This handles all HTTP methods on /all');
});

// Your code here

Hint

Use app.use((req, res) => { ... }) without a path to catch all unmatched requests.

4

Start the Express server

Add code to start the Express server listening on port 3000 and log 'Server running on port 3000' when it starts.

Express

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

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

app.all('/all', (req, res) => {
  res.send('This handles all HTTP methods on /all');
});

app.use((req, res) => {
  res.status(404).send('404 Not Found');
});

// Your code here

Hint

Use app.listen(3000, () => { ... }) to start the server and log a message.

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