Open llipengda opened 1 week ago
https://github.com/llipengda/next-redirect-bug
/test-a
redirect to /
/test-b
current: when clicking redirect to / in /test-b, redirect does not work. expected: redirect to /
redirect
Operating System: Platform: win32 Arch: x64 Version: Windows 11 Home China Available memory (MB): 16164 Available CPU cores: 16 Binaries: Node: 20.18.0 npm: 10.8.3 Yarn: 1.22.22 pnpm: 9.12.2 Relevant Packages: next: 15.0.3-canary.6 // Latest available version is detected (15.0.3-canary.6). eslint-config-next: N/A react: 19.0.0-rc-7c8e5e7a-20241101 react-dom: 19.0.0-rc-7c8e5e7a-20241101 typescript: 5.3.3 Next.js Config: output: N/A
Navigation
next dev (local), next start (local)
No response
Is this a bug, or was it designed to be this way? I deployed it on Vercel next-redirect-bug-gamma.vercel.app Can someone help me?
Link to the code that reproduces this issue
https://github.com/llipengda/next-redirect-bug
To Reproduce
/test-a
redirect to /
/test-b
redirect to /
Current vs. Expected behavior
current: when clicking
redirect to /
in/test-b
,redirect
does not work. expected: redirect to /Provide environment information
Which area(s) are affected? (Select all that apply)
Navigation
Which stage(s) are affected? (Select all that apply)
next dev (local), next start (local)
Additional context
No response