NextRequest constructor doesn't match Request behaviour for cloning

[tom-sherman]

Verify canary release

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

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000
    Binaries:
      Node: 18.13.0
      npm: 8.13.2
      Yarn: 1.22.19
      pnpm: 8.6.6
    Relevant Packages:
      next: 13.4.11-canary.0
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.9.4
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

App Router, Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue or a replay of the bug

https://github.com/tom-sherman/nextrequest-consructor-bug

To Reproduce

Attempt to clone the request like so:

const newRequest = new NextRequest(request)

Describe the Bug

Headers and body isn't preserved from request in route handlers and middleware.

Expected Behavior

As is with new Request(request), headers and body should be preserved/copied into the new request object.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-1468

[tom-sherman]

The workaround is to pass the original request in twice:

new NextRequest(request, request)

I suspect Next.js is only cloning the url from the first argument.

[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.