mirror of
https://github.com/hanzoai/next.js.git
synced 2026-10-30 14:46:38 +00:00
Jiachi LiuandGitHub
ee2bd3f00b
### What When client sends and Server Action request with `notFound()` inside, next-server will serve the RSC payload in response but we were also serving a fallback `robots=noindex` metadata for 404 requests. This will be a conflict for users custom metadata. The fallback `robots=noindex` for 404 response was for initially for pages rendering request. Here we skip it for the dynamic RSC to avoid user's metadata being de-prioritized due to the fallback `robots=noindex` taking precedence. We also add a test that it won't break form action, where when JS is disabled and notFound involked, the new page can still be served with fallback noindex Fixes NDX-953
17 lines
249 B
TypeScript
17 lines
249 B
TypeScript
'use client'
|
|
|
|
import { actionNotFound } from './action'
|
|
|
|
export default function Page() {
|
|
return (
|
|
<button
|
|
id="trigger-not-found"
|
|
onClick={() => {
|
|
actionNotFound()
|
|
}}
|
|
>
|
|
trigger not found
|
|
</button>
|
|
)
|
|
}
|