HTTP 425 Too Early
The server refuses to process a request that arrived as TLS 1.3 early data (0-RTT), because it could be replayed.
HTTP 425 Too EarlyHTTP/1.1 425 Too Earlystatus 425 too earlyEarly-Data: 1 425 Meaning
0-RTT requests can be replayed by an attacker, so servers reject non-idempotent ones with 425 and the client must retry after the handshake completes. Fix by disabling 0-RTT for sensitive endpoints, or make the client retry once the connection is fully established.
Common causes
- TLS 1.3 0-RTT early data enabled
- Non-idempotent request (POST) sent early
- CDN/proxy forwards
Early-Data: 1 - Client does not retry on 425
- Application not replay-safe
⚡ Quick fix
- Retry the request after the handshake
- Disable 0-RTT for POST/state-changing routes
- Honour the
Early-Dataheader in the app
Detailed fix by platform
Nginx
ssl_early_data off; # or on, with proxy_set_header Early-Data $ssl_early_data;
How to diagnose
- 0-RTT — Enabled?
- Request — Idempotent?
- Client — Retries?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in HTTP
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026