425 Too Early

A 425 Too Early status code indicates that the server is unwilling to risk processing a request that might be replayed.

Clients (user-agents and intermediaries) that sent the request in early data MUST automatically retry the request when receiving a 425 (Too Early) response status code. Such retries MUST NOT be sent in early data.

Intermediaries that receive a 425 (Too Early) status code MAY automatically retry requests after allowing the handshake to complete unless the original request contained the Early-Data header field when it was received. Otherwise, an intermediary MUST forward the 425 (Too Early) status code.

The server cannot assume that a client is able to retry a request unless the request is received in early data or the Early-Data header field is set to “1”. A server SHOULD NOT emit the 425 status code unless one of these conditions is met.

The 425 (Too Early) status code is not cacheable by default. Its payload is not the representation of any identified resource.

Notify me about new features:

upcoming free account access, charts & stats, historical data, API, etc.

* All fields required.