FAQ: Middleware - Route-Level app.use() - Single Path


#1

This community-built FAQ covers the “Route-Level app.use() - Single Path” exercise from the lesson “Middleware”.

Paths and Courses
This exercise can be found in the following Codecademy content:

Web Development

Learn Express

FAQs on the exercise Route-Level app.use() - Single Path

There are currently no frequently asked questions associated with this exercise – that’s where you come in! You can contribute to this section by offering your own questions, answers, or clarifications on this exercise. Ask or answer a question by clicking reply (reply) below.

If you’ve had an “aha” moment about the concepts, formatting, syntax, or anything else with this exercise, consider sharing those insights! Teaching others and answering their questions is one of the best ways to learn and stay sharp.

Join the Discussion. Help a fellow learner on their journey.

Ask or answer a question about this exercise by clicking reply (reply) below!

Agree with a comment or answer? Like (like) to up-vote the contribution!

Need broader help or resources? Head here.

Looking for motivation to keep learning? Join our wider discussions.

Learn more about how to use this guide.

Found a bug? Report it!

Have a question about your account or billing? Reach out to our customer support team!

None of the above? Find out where to ask other questions here!


#2

Just wondering, in the description of step 6 it says this:

app.use('/sorcerer', (req, res, next) => {
  console.log('User has hit endpoint /sorcerer');
  next();
});

In the example above the console will print 'User has hit endpoint /sorcerer' , if someone visits our web page’s ‘/sorcerer’ endpoint. Since the method app.use() was used, it won’t matter if the user is performing a GET ,a POST , or any other kind of HTTP request. Since the path was given as an argument to app.use() , this middleware function will not execute if the user hits a different path (for instance: '/spells' or '/sorcerer/:sorcerer_id' ).

However, in the exercise it seems that the middleware defined on path ‘/beans/:beanName’ will also respond to requests to ‘/beans/:beanName/add’ and ‘/beans/:beanName/remove’.

So, what exactly is the rule here? will a middleware respond to any request with a URL that is underneath the given path?