docs: clarify blocking route response status (#100191)
## What? - Correct examples that conflated not-found, forbidden, or unauthorized UI with a guaranteed HTTP status. - Clarify that `instant = false` does not buffer the HTTP response or guarantee a later `404`. - Update the streaming and status-code docs for Cache Components while keeping the existing `notFound()` example. - Clarify that HTML-limited bots wait for `generateMetadata`, after which the page can continue streaming. ## Why? The existing docs tied status commitment too closely to visible HTML and Suspense. With Cache Components, an empty prerendered shell can start the response before request-time rendering resumes. A later `notFound()`, `forbidden()`, or `unauthorized()` call renders its fallback UI and adds `noindex`, but it cannot change a committed `200` status. Proxy can provide an early request-time status. Redirects configured in `next.config.js` also run before page rendering and can return an HTTP redirect response. Supersedes: #99801 Related implementation PR: #99218 Related Discussion: #100192 ## Testing - Prettier on all changed files - MDX ESLint on all changed files - `git diff --check`
Showing
Please
register
or
sign in
to comment