redirect() function doesn't consider basePath

[XDean]

Verify canary release

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

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Enterprise
    Binaries:
      Node: 16.15.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.17-canary.2
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: N/A
    Next.js Config:
      output: N/A

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

App Router

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

https://github.com/XDean/next-bug/tree/redirect-function-basepath

To Reproduce

• Goto /dev/redirect
• It redirect to /target. The correct path should be /dev/target

Describe the Bug

The redirect function should consider basePath config. But it not.

Another strange behavior is, If you access /dev/link , click the link redirect to /direct, it works.

Expected Behavior

redirect('/target) can goto /dev/target

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

_NEXT-1529

[kmvan]

I don't think this is a bug.

[XDean]

I don't think this is a bug.

Please give some reason.

Someone may say 'this is by design', I prepared another testcase.

• goto /dev/link
• clik the link redirect to /direct, it works
• right click the link redirect to /direct, open in new tab, it fails.

The behavior is not consistent.

[timneutkens]

This is definitely a bug 👍

[kmvan]

@XDean You are right.

[github-actions]

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