4xx Client error

425 Too Early

The server won't process a request that might be replayed.

What 425 means

Sent for requests in TLS 1.3 early data (0-RTT), which attackers could replay. The client should resend after the handshake.

Common causes

A request sent as TLS early data.

How to fix it

If you're calling an API

Retry; clients normally do this automatically.

If you run the server

Only accept idempotent requests in early data.

Should you retry?

Yes, after the TLS handshake completes.

Example response

HTTP

HTTP/1.1 425 Too Early
Content-Type: application/problem+json

{
  "type": "about:blank",
  "title": "Too Early",
  "status": 425,
  "detail": "The server won't process a request that might be replayed."
}

Defined in: RFC 8470. 425 is a client error: change the request before retrying.

Debugging an API call? Convert your request with the cURL converter, check the response with the JSON formatter, or see whether the API is down on its status page.

HTTP 425 FAQ

What does HTTP 425 mean?

425 Too Early: The server won't process a request that might be replayed. Sent for requests in TLS 1.3 early data (0-RTT), which attackers could replay. The client should resend after the handshake.

Is 425 a client or server error?

It's a client error (4xx): something about the request needs to change before it can succeed.

How do I fix a 425 error?

Retry; clients normally do this automatically.

Should I retry after a 425?

Yes, after the TLS handshake completes.

Other 4xx status codes

All HTTP status codes