You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
docs: Catch makes erroring routes uncacheable — document after RC #8913
An SSR-caught <ErrorBoundary> error still responds 200, so the router sends Cache-Control: no-store and skips its SSR cache (#8745). A route is not cached while it errors, which can increase SSR costs if the error happens to all active users all at once.
Document after RC: the cost, and the way out — throw the failure as an error response (httpError()) instead of an inline fallback.
changed the title [-]docs: ErrorBoundary makes erroring routes uncacheable — document after RC[/-][+]docs: Catch makes erroring routes uncacheable — document after RC[/+]on Sep 29, 2026
Activity
[-]docs: ErrorBoundary makes erroring routes uncacheable — document after RC[/-][+]docs: Catch makes erroring routes uncacheable — document after RC[/+]