fix: handle server routes with exact match

Author: schiller-manuel

packages/start-server-core/src/createStartHandler.ts

@@ -349,18 +349,22 @@ async function handleServerRoutes({
   let url = new URL(request.url)
   url = executeRewriteInput(router.rewrite, url)
   const pathname = url.pathname
+  // this will perform a fuzzy match, however for server routes we need an exact match
+  // if the route is not an exact match, executeRouter will handle rendering the app router
+  // the match will be cached internally, so no extra work is done during the app router render
   const { matchedRoutes, foundRoute, routeParams } =
     router.getMatchedRoutes(pathname)
 
+  const isExactMatch = foundRoute && routeParams['**'] === undefined
+
   // TODO: Error handling? What happens when its `throw redirect()` vs `throw new Error()`?
 
   const middlewares = flattenMiddlewares(
     matchedRoutes.flatMap((r) => r.options.server?.middleware).filter(Boolean),
   ).map((d) => d.options.server)
 
   const server = foundRoute?.options.server
-
-  if (server) {
+  if (server && isExactMatch) {
     if (server.handlers) {
       const handlers =
         typeof server.handlers === 'function'