Skip to the content

425 Too Early

The server won't process a request that was sent as TLS early data, because a request sent that way could be replayed.

Class
4xx Client error. The request is the problem: a wrong address, missing credentials, data the server can't accept.
Defined in
RFC 8470

Share this tool:TwitterFacebookLinkedInWhatsAppEmail

What causes it

TLS 1.3 lets a returning client send its first request along with the handshake, which saves a round trip. Someone who records that data can send it again. A server that finds the request too risky to carry out twice, a payment for instance, answers 425.

What to do about it

Send the request again once the handshake has finished. Browsers do that by themselves, so visitors never see this code. If you call an API from your own code with early data switched on, handle a 425 with one retry.

If you run a server behind a CDN or proxy that accepts early data: it marks such requests with an Early-Data: 1 header, and it is up to your application to refuse the ones that are not safe to repeat.

All codes are on the list of HTTP status codes, which can be searched by number and by word.

See all 12