Using redirect to the redirect to the same path within server actions causes the page to do a browser refresh when using runtime = edge

[Fredkiss3]

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 23.0.0: Tue Aug  1 03:25:17 PDT 2023; root:xnu-10002.0.242.0.6~31/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 8.6.7
    Relevant Packages:
      next: 13.4.15
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A

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

App Router, Routing (next/router, next/navigation, next/link)

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

https://github.com/Fredkiss3/next-redirect-cache-bug/tree/another-bug

To Reproduce

1. clone and run the server
2. Click on the button redirect To / it will submit a form which redirects you to the same page, you will see a browser refresh
3. Click on the button redirect To /target it will submit a form which redirects you to /target page you won't see a browser refresh

Enregistrement.de.l.ecran.2023-08-15.a.00.14.36.mov

Describe the Bug

When calling redirect to the same page inside a server action, nextjs does a full browser refresh, while redirecting to another page does not.

This only happens when using edge runtime.

Expected Behavior

It should not do a browser refresh but a client-side navigation.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[nextjs-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.

[nextjs-bot]

This issue has been automatically closed due to two years of inactivity. If you’re still experiencing a similar problem or have additional details to share, please open a new issue following our current issue template. Your updated report helps us investigate and address concerns more efficiently. Thank you for your understanding!