Request path includes API gateway stage twice

[dcchut]

Background

I have an API gateway hooked up to a lambda - I don't have any parameter mappings & I'm not using a custom domain. The lambda uses lambda_http together with axum. The API gateway has a stage called Prod, the invoke URL is along the lines of:

https://blablabla.execute-api.ap-southeast-2.amazonaws.com/Prod

Current outcome

When performing a request such as POST https://blablabla.execute-api.ap-southeast-2.amazonaws.com/Prod/auth/login,
lambda_http rewrites the request path to /Prod/Prod/auth/login.

Expected outcome

I would expect the request path to be /Prod/auth/login.

Other information

While there is a workaround (rewrite the path in middleware), the underlying behavior of including the stage twice is very surprising to me - is is possible I've misconfigured something?

Related discussion in #107 and #450.

[calavera]

Are you using APIGW Rest or HTTP? I wonder if APIGW started sending the stage in the path.

Can you print the content of req.raw_http_path()? That should not have the stage part. If it does, the event's data has changed.

[dcchut]

HTTP. req.raw_http_path() is /Prod/auth/login.

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for the maintainers of this repository to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.