Files
JJ KasperandGitHub 3e022577f2 Fix resolvedPathname for middleware rewrite (#81144)
This updates the handling of `resolvedPathname` to handle the case we
don't know the `rewroteURL` for example when it's a middleware rewrite
and we can't derive it since it's fully dynamic. Since we always know
the `srcPage` we can always recreate the final URL using the params
which this does as it's more reliable than relying on the parsed URL as
a backup.

Validated against our deploy tests
https://github.com/vercel/next.js/actions/runs/16014327609/job/45178072108
and
https://github.com/vercel/vercel/actions/runs/16014347060/job/45178081995?pr=13509

x-ref: [slack thread](https://vercel.slack.com/archives/C093RLQ7RGC)
2025-07-01 20:53:54 -07:00

14 lines
496 B
TypeScript

import { headers } from 'next/headers'
export default async function Home() {
const headersList = await headers()
console.log('headers', headersList.get('x-nextjs-cache'))
return (
<div className="grid grid-rows-[20px_1fr_20px] items-center justify-items-center min-h-screen p-8 pb-20 gap-16 sm:p-20 font-[family-name:var(--font-geist-sans)]">
<main className="flex flex-col gap-[32px] row-start-2 items-center sm:items-start">
Render next
</main>
</div>
)
}