Add an option to disable the wildcard route or to select the ones to be enabled

[edocrippaofficial]

Prerequisites

• I have written a descriptive issue title
• I have searched existing issues to ensure the feature has not already been requested

🚀 Feature Proposal

The proposal is to have a way to select what route to create between the standard one and the one with the wildcard.

This is the current implementation (both routes are created):

fastify.route({
    url: '/',
    method: opts.httpMethods || httpMethods,
    preHandler,
    config: opts.config || {},
    constraints: opts.constraints || {},
    handler
})
fastify.route({
    url: '/*',
    method: opts.httpMethods || httpMethods,
    preHandler,
    config: opts.config || {},
    constraints: opts.constraints || {},
    handler
})

There may be an option to disable the wildcard route or to select those to be enabled.
I can do this myself if the idea seems reasonable.

Motivation

If I want to create a route for the /foo path, I also want Fastify to return a 404 response to the /foo/bar route, without trying to forward it to the downstream if not wanted.

Example

No response

[simone-sanfratello]

I'm not sure to add this logic on routing, I think it's not proxy responsibility. Could you describe a real world example where this feature solves the issues?

[mcollina]

I think this would be useful to add, basically providing a list of method/pattern to expose.

[edocrippaofficial]

@simone-sanfratello with the wildcard path basically forwards every path that matches the given prefix, but perhaps you want to restrict access only to the API exposed by the downstream server.

I use fastify-swagger and, looking at the result, I see that the /prefix/* API is also available. This may cause me to attempt some unwanted requests to the downstream service, resulting in wasted network time and downstream service usage. If there was an option to optionally set the wildcard, it would be more manageable for a reverse-proxy scenario where this library is used, so that the proxy can terminate the request on its own if the path is not supported.