Vercel / Deployment

Bug: history.pushState to a new URL reverts when route has a prefetched Link + proxy.ts cookie-based redirect

Fix Next.js URL reversion bug where client-side navigation via history.pushState gets reverted by RSC tree when middleware uses proxy.ts with cookies Includes evidence for Vercel troubleshooting demand.

Source-backed Last updated May 18, 2026 1 source Needs local verification

Category: Deployment
Error signature: history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect
Quick fix: Compare the failing environment with a known working setup, then change one configuration value at a time.
Updated: May 18, 2026
Verification status: Source-backed
Evidence: 1 public source URL

Before you change production

This page includes public source URLs in the imported troubleshooting record. Compare those references with your version and environment before applying changes.

Reproduce the smallest failing action and save non-secret logs before changing configuration.
Check versions for Vercel, related SDKs, package managers, CI runners, and hosting providers.
Change one setting or dependency at a time, then rerun the same failing command or request.
Avoid destructive commands, credential rotation, billing changes, or security relaxations without a rollback plan.

What this error means

history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect is a Vercel failure pattern reported for developers trying to fix next.js url reversion bug where client-side navigation via history.pushstate gets reverted by rsc tree when middleware uses proxy.ts with cookies. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub issue #93923 in vercel/next.js (opened May 18, 2026). In Next.js 16.x, calling history.pushState to navigate to a new URL on the same route appears to succeed but immediately reverts within ~1 frame. Server-rendered RSC tree remains for old URL. Affected areas: Middleware, Linking and Navigating, Runtime, Dynamic Routes. Has minimal repro repo.

Common causes

GitHub issue #93923 in vercel/next.js (opened May 18, 2026). In Next.js 16.x, calling history.pushState to navigate to a new URL on the same route appears to succeed but immediately reverts within ~1 frame. Server-rendered RSC tree remains for old URL. Affected areas: Middleware, Linking and Navigating, Runtime, Dynamic Routes. Has minimal repro repo.

Quick fixes

Confirm the exact error signature matches history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect.
Check the Vercel account, local tool state, and provider configuration involved in the failing workflow.
Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

Verify the command, editor, extension, or API client that produced the error.
Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

Capture the exact error message and the command, editor action, or request that triggered it.
Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
Review the source evidence below and compare it with your environment.
Apply one change at a time and rerun the smallest failing action.
Keep the working fix documented for the team or deployment environment.

How to prevent it

Keep provider/tool configuration documented.
Record non-secret diagnostics such as tool version, provider name, model name, and command path.
Add a lightweight check before CI or production workflows depend on the tool.

Diagnostic flow for this page

Match history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect exactly before applying the quick fix.
Compare the failing environment with Vercel versions, account scope, provider settings, and deployment context.
Check the listed common causes in order, starting with the cause that best matches your logs.
Use the evidence status below to decide whether to confirm against public sources or official documentation.
Apply one reversible change, rerun the smallest failing action, and keep rollback notes.

FAQ

What does history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect mean in Vercel?

history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect indicates the workflow described by "Bug: history.pushState to a new URL reverts when route has a prefetched Link + proxy.ts cookie-based redirect" failed in a Deployment context. Start by confirming the exact signature and the component that emitted it.

What should I check first for history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect?

Check whether this cause matches your environment: GitHub issue #93923 in vercel/next.js (opened May 18, 2026). In Next.js 16.x, calling history.pushState to navigate to a new URL on the same route appears to succeed but immediately reverts within ~1 frame. Server-rendered RSC tree remains for old URL. Affected areas: Middleware, Linking and Navigating, Runtime, Dynamic Routes. Has minimal repro repo.

Is the history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect guidance source-backed?

The "Bug: history.pushState to a new URL reverts when route has a prefetched Link + proxy.ts cookie-based redirect" page is labeled source-backed. It has 1 public source URL from github.com, so use that evidence status when deciding how much additional verification you need.

When should I avoid the quick fix for history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect?

For "Bug: history.pushState to a new URL reverts when route has a prefetched Link + proxy.ts cookie-based redirect", avoid applying "Compare the failing environment with a known working setup, then change one configuration value at a time." when the error text differs, the affected version or provider is different, or the change would touch credentials, billing, DNS, production deploy settings, or irreversible data.

What should I collect before debugging history.pushState to a new URL reverts when route has a prefetched <Link> + proxy.ts cookie-based redirect?

For "Bug: history.pushState to a new URL reverts when route has a prefetched Link + proxy.ts cookie-based redirect", collect the failing Vercel command or request, non-secret configuration, versions, timestamps, request IDs when available, and the smallest reproduction that still triggers the signature.