# HTTP 425 Too Early

**Code:** `425` · **Category:** HTTP · **Seen on:** HTTP, Nginx

The server refuses to process a request that arrived as TLS 1.3 early data (0-RTT), because it could be replayed.

## 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

1. Retry the request after the handshake
2. Disable 0-RTT for POST/state-changing routes
3. Honour the `Early-Data` header in the app

## Detailed fix by platform

### Nginx

1. `ssl_early_data off;   # or on, with proxy_set_header Early-Data $ssl_early_data;`

## How to diagnose

1. **0-RTT** — Enabled?
2. **Request** — Idempotent?
3. **Client** — Retries?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/http/425-too-early)
