I have found something that may help.

node_modules\koa-router\lib\router.js

 335 var mostSpecificLayer = matchedLayers[matchedLayers.length - 1];
 336 ctx._matchedRoute = mostSpecificLayer.path;

As shown in the code, ctx._matcheRoute is the most matched route path insteadof requested.

I ran into the same problem. The issue is, that matchedLayers contains - as the name suggests - all matched layers, that will be put in the middleware-chain (because the regex matches).

In the case above, it's because :orderId could also be list. So, if the orderId-Middleware decides, it doesn't want to handle the request, it can call next() and the list-route will be called. That way the "mostSpecificLayer" isn't necessarily the "last" or "current" one.

With that being said, the ctx._matchedRoute is probably a bug - or at least misleadingly named.

I've created PR #524, which would populate ctx.routerPath

@schwarmco this is the official one from koa org https://github.com/koajs/router , a fork of this repo

@tuananh thanks - i opened a pull-request there... just landed here, because i searched for this exact same issue :)

Thanks very much, I have some things I did not pay attention to this issue in time, sorry!

Already got help：https://github.com/koajs/router/releases/tag/v9.1.0 Thx!!!!!