Reading request bodies in middleware breaks API requests

[AliYusuf95]

Verify canary release

• I verified that the issue exists in Next.js canary release

Provide environment information

    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64
    Binaries:
      Node: 16.15.1
      npm: 8.11.0
      Yarn: 1.22.15
      pnpm: 7.2.1
    Relevant packages:
      next: 12.1.7-canary.41
      react: 17.0.2
      react-dom: 17.0.2

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

I'm trying to implement ory kratos self-service login flow. As their documentation, I used @ory/integrations package to integrate with Next.js. The integration basically utilizes the next API paths to proxy incoming requests to ory kratos instance. This approach works fine until [email protected]. This release brings the ability to read the body in middleware #34519. This feature breaks the ability to correctly proxy requests (specifically pip and other req functions usage).

Expected Behavior

Should be able to utilize the full functionality of request IncomingMessage API without losing context.

Link to reproduction

https://github.com/AliYusuf95/kratos-selfservice-ui-react-nextjs

To Reproduce

1- Try to send a POST request method to http://localhost:3000/api/test and observe the response method and headers, then remove/rename middleware.ts file and try again.

2- Follow the documentation page to run ory kratos instance, the project will not work if middleware.ts is present.

[AliYusuf95]

Reference related issue in ory/integrations#34

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.