docs: note per-route cost of boundary files, cached Route Handler checks, and…
docs: note per-route cost of boundary files, cached Route Handler checks, and per-instance rate limits (#100985) ## Summary - `not-found.mdx`, `forbidden.mdx`, `unauthorized.mdx`: each of these files is sent with every route under its segment, even when the route never calls `notFound()`, `forbidden()`, or `unauthorized()`, and the Client Components it imports load on those pages. For the root `app/not-found.js`, that is every page of the app. - `backend-for-frontend.mdx`, rate limiting: a counter kept in memory applies per server instance and resets on restart. - `backend-for-frontend.mdx`, access to protected resources: a response cached with `Cache-Control: public` can be served by a CDN without running the handler, so its checks do not apply to cache hits. Commits: - docs: note boundary files ship with every route, cached Route Handler responses skip checks, and in-memory rate limits are per instance <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment