mirror of
https://github.com/hanzoai/next.js.git
synced 2026-10-30 14:46:38 +00:00
74153e1208
I think that sometimes when a revalidation happens from a request with caching headers this causing the 304 status to be cached. This PR ensures the 304 from an initial response doesn't affect a background revalidation. Fixes: https://github.com/vercel/next.js/issues/56580 --------- Co-authored-by: JJ Kasper <[email protected]>
10 lines
208 B
JavaScript
10 lines
208 B
JavaScript
export default async function Page() {
|
|
const time = await new Promise((resolve) => {
|
|
setTimeout(500, resolve(new Date().getTime()))
|
|
})
|
|
|
|
return <div>Time: {time}</div>
|
|
}
|
|
|
|
export const revalidate = 1
|