When previousMiddleware returns body middleware does not return

[vincentdigital]

Hey all,

I found that when I pass previousMiddleware to instantiate the middleware, like so;

  const redirectionIoMiddleware = createRedirectionIoMiddleware({
    previousMiddleware: localMiddleware,
    mode: "full",
    logged: true,
  });

where localMiddleware returns something like this:

  return NextResponse.json(
    { message: "test" },
    {
      status: 200,
    }
  );

that the redirection.io middleware still processes and not just returns the response from the earlier middleware as I would expect. Given that middleware are allowed to also return a full response according to next.js docs, I would say this is a bug. Any considerations or thoughts?

[joelwurtz]

This is caused by the way middleware works in next.js :

When a middleware want to pass the request to the backend (or next middleware), the docs says that you should do the following :

return Response.next();

Which in details will create a Response object with a 200 status code

So basically in our code when we received a response in 200 from the previous middleware, we consider this use case and we process the request ignoring this response.