Setting the file. One moment.
Subchapter 7.43
references/support-topics/next-route-handler-get-cache-defaults.mdMarkdown1 KBView on GitHub
On Next.js 15+, GET Route Handlers are dynamic by default. For hot public GET handlers, verify whether uncached behavior is intentional before recommending cache headers or route config.
Use method share, cache result, and source. Check GET, revalidate, dynamic, request headers, cookies, auth, query params, and response Cache-Control.
Do not cache POST-style handlers, webhooks, per-user APIs, streaming responses, search requests with user-specific params, or handlers that read auth/cookies.
Name the Next.js version, GET share, cache result mix, and the exact handler or header line that makes public caching safe.