- Home
- Tools
- Developer Tools
- HTTP Status Codes
- 425 Too Early
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
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.
Other 4xx codes
- 400 Bad Request
- 401 Unauthorized
- 402 Payment Required
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- 411 Length Required
- 412 Precondition Failed
- 413 Content Too Large
- 414 URI Too Long
- 415 Unsupported Media Type
- 416 Range Not Satisfiable
- 417 Expectation Failed
- 418 I'm a teapot
- 421 Misdirected Request
- 422 Unprocessable Content
- 423 Locked
- 424 Failed Dependency
- 426 Upgrade Required
- 428 Precondition Required
- 429 Too Many Requests
- 431 Request Header Fields Too Large
- 451 Unavailable For Legal Reasons