WhereGoes

425 Too Early

4xx client error

The server declined to process a replayable request because it might be replayed after the TLS handshake, guarding transactional requests against replay attacks.

Common causes

  • A request was sent as early data on a resumed TLS session.
  • The server rejects early data for idempotency reasons.
  • A 0-RTT client retries on a full handshake.

How to fix it

  • Retry the request after the full TLS handshake completes.
  • Send replay-sensitive requests only on established connections.
  • Advertise the policy so clients stop using 0-RTT for writes.

What it means for redirects and SEO

Replay protection can reject legitimate retried requests from bots. Rare in practice. Only enable it on endpoints that truly need anti-replay.

Related codes