requests to /foo/bar to an API Gateway (v1) resource of /foo/{proxy+} return 404 as they are routed to /bar

I'm having the same issue as in this comment https://github.com/vendia/serverless-express/issues/454#issuecomment-1322898350 (should be probably reopened?)

Upgraded from the legacy `aws-serverless-express` and for some reason it takes the path from `pathParameters.proxy` (which is `bar`) and not the request.path (which is `/foo/bar`)

I'll be happy to work on a PR if you indeed confirm it's a bug

Start by reproducing an API Gateway v1 request to the /foo/{proxy+} resource and compare pathParameters.proxy with request.path. Trace how the request path is selected after upgrading from aws-serverless-express, using the linked issue comment as context. Done means /foo/bar reaches the Express application as /foo/bar rather than /bar, with a regression test covering the behavior.

Vom Indexierungsmodell aus dem Issue-Text verfasst.