Route matching order matters in Express - Cheat Sheet & Quick Revision

Recall & Review

beginner

What happens if you place a general route before a specific route in Express?

The general route will match first and handle the request, so the specific route will never be reached.

beginner

Why does route order matter in Express?

Express checks routes in the order they are defined and stops at the first match. So, order controls which route handles a request.

intermediate

Given these routes, which one matches the URL '/user/profile'?
app.get('/user/profile', ...)
app.get('/user/:id', ...)

If /user/:id is defined before /user/profile, it will match '/user/profile' as id='profile'. So order matters to get the right route.

beginner

How can you ensure a specific route is matched before a general one?

Define the specific route first in your code, then the general route after it.

intermediate

What is the effect of placing a wildcard route like app.get('*', ...) at the top?

It will catch all requests and prevent any other routes from running, blocking specific routes below it.

In Express, which route should be defined first to correctly handle '/user/profile'?

A app.get('/user', ...)

B app.get('/user/:id', ...)

C app.get('*', ...)

D app.get('/user/profile', ...)

Specific routes like '/user/profile' should be defined before parameter routes like '/user/:id' to match correctly.

What happens if you put a wildcard route app.get('*', ...) before other routes?

A It will match only GET requests to '/'

B Other routes will never be reached.

C It will be ignored.

D It will only match unknown routes.

Wildcard routes catch all requests and block routes defined after them.

Express matches routes in which order?

A Alphabetical order

B By route length

C Order routes are defined in code

D Random order

Express checks routes in the order they appear in the code.

If you want a route to catch all unmatched requests, where should you place it?

A At the bottom of the route list

B In the middle of the route list

C At the top of the route list

D Anywhere, order does not matter

Catch-all routes should be last to avoid blocking other routes.

Which route will match '/user/123' if defined in this order?
1. app.get('/user/:id', ...)
2. app.get('/user/profile', ...)

A /user/:id

B /user/profile

C Both routes

D No route

The first matching route '/user/:id' will handle '/user/123'.

Explain why the order of route definitions matters in Express and give an example.

Think about how Express stops checking after the first match.

Describe what happens if a wildcard route is placed before other routes in Express.

Consider the effect of a catch-all route on routing.

Practice

1. In Express, why does the order of route definitions matter?
app.get('/user', ...) and app.get('/:id', ...) are defined. Which route will handle /user if /:id is defined first?

easy

A. The most specific route always handles the request regardless of order.

B. Express matches all routes and runs all handlers regardless of order.

C. The first matching route in order handles the request, so /:id will handle /user.

D. Express throws an error if routes overlap.

Solution

1. Step 1: Understand Express route matching order

   Express checks routes in the order they are defined and stops at the first match.

2. Step 2: Analyze the given routes

   If /:id is defined before /user, the path /user matches /:id first, so that handler runs.

3. Final Answer:

   The first matching route in order handles the request, so /:id will handle /user. -> Option C

4. Quick Check:

   Route order controls matching = C [OK]

Hint: Remember: Express uses first match wins rule [OK]

Common Mistakes:

• Thinking Express runs all matching routes
• Assuming specific routes override order automatically
• Believing Express throws errors on overlapping routes

2. Which of the following is the correct way to define routes so that /about is handled before any dynamic /:page route in Express?

easy

A. app.get('/:page', handler); app.get('/about', handler);

B. app.get('/about', handler); app.get('/:page', handler);

C. app.get('/about', handler); app.use('/:page', handler);

D. app.use('/:page', handler); app.get('/about', handler);

Solution

1. Step 1: Recall route order importance

   Specific routes like /about must be defined before dynamic routes like /:page to match first.

2. Step 2: Check options for correct order

   app.get('/about', handler); app.get('/:page', handler); defines /about first, then /:page, ensuring /about matches before dynamic routes.

3. Final Answer:

   app.get('/about', handler); app.get('/:page', handler); -> Option B

4. Quick Check:

   Specific before dynamic = A [OK]

Hint: Put specific routes before dynamic ones [OK]

Common Mistakes:

• Defining dynamic routes before specific ones
• Using app.use instead of app.get for specific routes
• Assuming order doesn't affect matching

3. Given the following Express routes:

app.get('/product/:id', (req, res) => res.send('Product ' + req.params.id));
app.get('/product/list', (req, res) => res.send('Product List'));

What will be the response when a client requests /product/list?

medium

A. 'Product List'

B. 'Product list'

C. 404 Not Found

D. Error: Route conflict

Solution

1. Step 1: Check route order

   The dynamic route /product/:id is defined before the specific /product/list route.

2. Step 2: Determine which route matches first

   Request /product/list matches /product/:id first, so it returns 'Product list'.

3. Step 3: Check case sensitivity

   The specific route sends 'Product List' with capital 'L', while the dynamic route sends 'Product ' + id, which would be 'Product list' if matched.

4. Final Answer:

   'Product List' -> Option A

5. Quick Check:

   Specific route matches only if defined before dynamic [OK]

Hint: First matching route runs, order matters for specific vs dynamic [OK]

Common Mistakes:

• Assuming specific route matches first regardless of order
• Expecting 404 when dynamic route matches
• Thinking Express throws route conflict errors

4. You have these Express routes:

app.get('/:category', handler1);
app.get('/books', handler2);

Requests to /books always go to handler1. How do you fix this?

medium

A. Move app.get('/books', handler2) before app.get('/:category', handler1).

B. Change /:category to /category/:name.

C. Use app.use instead of app.get for /books.

D. Rename /books to /books/all.

Solution

1. Step 1: Identify route order problem

   The dynamic route /:category matches /books first because it is defined before the specific route.

2. Step 2: Fix by reordering routes

   Moving the specific /books route before the dynamic one ensures /books matches handler2 first.

3. Final Answer:

   Move app.get('/books', handler2) before app.get('/:category', handler1). -> Option A

4. Quick Check:

   Specific routes before dynamic fix matching [OK]

Hint: Place specific routes above dynamic routes [OK]

Common Mistakes:

• Changing route paths unnecessarily
• Using app.use instead of app.get incorrectly
• Ignoring route order importance

5. You want to create an Express app where:
- /api/users returns a user list
- /api/:resource returns data for any resource

How should you order these routes to ensure /api/users returns the user list and /api/products returns product data?

hard

A. Define /api/:resource first, then /api/users.

B. Combine both routes into one with conditional logic inside.

C. Use app.use for /api/users and app.get for /api/:resource.

D. Define /api/users first, then /api/:resource.

Solution

1. Step 1: Understand route specificity and order

   Specific routes like /api/users must be defined before dynamic routes like /api/:resource to match correctly.

2. Step 2: Apply correct order

   Defining /api/users first ensures requests to /api/users hit that route, while other resources match the dynamic route.

3. Final Answer:

   Define /api/users first, then /api/:resource. -> Option D

4. Quick Check:

   Specific before dynamic for correct matching [OK]

Hint: Always put specific API routes before dynamic ones [OK]

Common Mistakes:

• Defining dynamic route before specific API routes
• Using app.use incorrectly for route handlers
• Trying to merge routes instead of ordering