Double redirect in RSC page when using a loading boundary

Link to the code that reproduces this issue

https://github.com/PaulWild/multiple-redirects-in-rsc/

To Reproduce

• go to /
• Server component will redirect to /api/redirect
• The api route is called twice as seen by the terminal logs.

Current vs. Expected behaviour

The api route should only be called once

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Jan 11 04:09:03 UTC 2024
  Available memory (MB): 15935
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.3.0-canary.62 // Latest available version is detected (14.3.0-canary.62).
  eslint-config-next: N/A
  react: 19.0.0-beta-4508873393-20240430
  react-dom: 19.0.0-beta-4508873393-20240430
  typescript: 5.1.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Navigation

Which stage(s) are affected? (Select all that apply)

next dev (local), Vercel (Deployed)

Additional context

This doesn't happen if there aren't any loading pages. This seems to be related to https://github.com/vercel/next.js/issues/57257

Start with the reproduction repository linked in the issue, visit /, and trace the server component redirect to /api/redirect while a loading boundary is present. Compare the terminal request count with and without loading pages; done means the API route is called once in the affected dev and deployed scenarios.