Middleware makes request body null even if route is not matched.
Unanswered
Masai Lion posted this in #help-forum
Masai LionOP
I have a very basic setup with /api/ endpoints.
Even though the middleware is not triggered (not matched) to the api route (which i confirm it doesnt), it does remove the body of a POST request to the api route.
Removing the middleware file fixes the issue.
Found many issues regarding that (https://github.com/vercel/next.js/issues/39262, https://github.com/vercel/next.js/issues/30953, https://github.com/orgs/vercel/discussions/1521).
But none of them still active.
Anyone experiencing this recently?
Even though the middleware is not triggered (not matched) to the api route (which i confirm it doesnt), it does remove the body of a POST request to the api route.
Removing the middleware file fixes the issue.
Found many issues regarding that (https://github.com/vercel/next.js/issues/39262, https://github.com/vercel/next.js/issues/30953, https://github.com/orgs/vercel/discussions/1521).
But none of them still active.
Anyone experiencing this recently?