Skip to content

docs: Catch makes erroring routes uncacheable — document after RC #8913

Open

Description

@maiieul

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.

Activity

  1. 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    V2docsImprovements or additions to documentationrouter

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions