HTTP 425 Too Early

HTTP 425 Too Early (RFC 8470) indicates the server is unwilling to risk processing a request that might be replayed. This is specifically related to TLS 1.3 early data (0-RTT) — data sent in the first flight of a TLS handshake can be replayed by an attacker. Non-idempotent requests (POST, PUT, DELETE) sent as early data may be dangerous, so the server returns 425 to tell the client to retry after the full handshake completes.

Debug HTTP 425 live

Analyze real 425 behavior — headers, caching, CORS, redirects

Open Inspector →

Try it (live endpoint)

Response includes the status code, standard headers (including Content-Type), and a small diagnostic JSON body describing the request and returned status.

Simulator URL (copy in the app after load — not a normal link):

https://httpstatus.com/api/status/425

Example request:

curl -i "https://httpstatus.com/api/status/425"

Try in playground

Meaning

Indicates that the server is unwilling to risk processing a request that might be replayed.

What it guarantees

The request was not fulfilled due to a client-side issue.

What it does NOT guarantee

Retries will succeed without changing request inputs.
The server is healthy; it may still be failing for other reasons.

When to use this status

Validation fails (missing fields, invalid types, invalid params).
A required header is missing or malformed (Content-Type, Authorization).
The client is not allowed to perform the operation.

When NOT to use this status (common misuses)

Using 400 for authentication/authorization failures.

Clients cannot distinguish validation vs auth; retry/login flows break.

Using 404 to mask permission issues everywhere.

Monitoring misclassifies access bugs; SEO can degrade if real pages appear missing.

Returning 4xx for server-side bugs.

Clients stop retrying; incidents are masked as client behavior.

Critical headers that matter

Content-Type

Defines error body format (JSON/text/problem+json).

Clients can’t parse structured errors; observability loses fidelity.

Cache-Control

Prevents caching transient errors unless intended.

CDNs cache failures; prolonged user-visible outages.

Tool interpretation

Browsers

Displays an error state; devtools exposes status and headers. Cache headers can accidentally cache error documents.

API clients

Classifies as failure; retry policy depends on idempotency and code class. Structured errors improve handling.

Crawlers / SEO tools

Persistent failures reduce crawl rate; soft-404 patterns cause indexing instability.

Uptime monitors

Typically alerts based on rate/threshold. Consistent classification reduces false positives.

CDNs / reverse proxies

May cache errors if misconfigured; respects Cache-Control and can serve stale on origin failure.

Inspector preview (read-only)

On this code, Inspector focuses on semantics, headers, and correctness warnings that commonly affect clients and caches.

Signals it will highlight

Status semantics vs method and body expectations
Header sanity (Content-Type, Cache-Control, Vary) and evidence completeness
Error cacheability and retry guidance signals

Correctness warnings

No common correctness warnings are specific to this code.

Guided Lab outcome

Reproduce HTTP 425 Too Early using a controlled endpoint and capture the full exchange.
Practice distinguishing status semantics from transport issues (redirects, caching, proxies).
Identify the minimum request changes required to move from client error to success.

Technical deep dive

HTTP 425 Too Early has specific technical implications for API design, caching, and client behavior. Understanding the precise semantics helps distinguish it from similar status codes and implement correct error handling. The response should include a descriptive body following a consistent error schema (like RFC 7807 Problem Details) so clients can programmatically handle the error.

Real-world examples

REST API returning 425

A well-designed API returns 425 Too Early with a structured error body containing the error type, human-readable message, and machine-readable code. The client uses this to display an appropriate error message or take corrective action.

Web application encountering 425

A web application receives 425 from an API call. The frontend error handler maps the status code to a user-friendly message and either prompts the user to correct their input, retry the request, or contact support.

Monitoring and alerting for 425

An observability system tracks 425 Too Early responses. Client errors (4xx) are typically logged at WARN level since they indicate client issues, not server problems. Spikes in 425 responses may indicate a broken client deployment or API contract change.

Framework behavior

Express.js (Node)

Express: res.status(425).json({ error: 'Too Early', message: 'Descriptive error' }). Custom error middleware: app.use((err, req, res, next) => { if (err.status === 425) res.status(425).json(err.body); });

Django / DRF (Python)

Django REST Framework handles 425 through exception classes. Custom: raise APIException(detail='Error message', code=425). DRF's exception_handler formats consistent error responses.

Spring Boot (Java)

Spring: throw new ResponseStatusException(HttpStatus.valueOf(425), "Error message"). Or use @ControllerAdvice to handle specific exception types and return 425 with structured error bodies.

FastAPI (Python)

FastAPI: raise HTTPException(status_code=425, detail='Error message'). Custom exception handler: @app.exception_handler(CustomError) to return 425 with structured error responses.

Debugging guide

Read the full response body — well-designed APIs include error details explaining why 425 was returned
Check request headers (Authorization, Content-Type, Accept) — many 425 errors stem from missing or incorrect headers
Compare your request against the API documentation — verify required fields, parameter types, and URL format
Use curl -v or httpie to reproduce the request and see the full HTTP exchange
Check server logs for additional context — the response body may be a sanitized version of a more detailed server-side error

Code snippets

Node.js

// Handle 425 Too Early in Express
app.use((err, req, res, next) => {
  if (err.status === 425) {
    return res.status(425).json({
      type: 'https://api.example.com/errors/too-early',
      title: 'Too Early',
      status: 425,
      detail: err.message
    });
  }
  next(err);
});

Python

from fastapi import HTTPException

# Raise 425 Too Early
raise HTTPException(
    status_code=425,
    detail={
        'type': 'too_early',
        'message': 'Descriptive error for 425 Too Early'
    }
)

Java (Spring)

// Spring Boot 425 Too Early handling
@ExceptionHandler(CustomTooEarlyException.class)
public ResponseEntity<ErrorResponse> handleTooEarly(
        CustomTooEarlyException ex) {
    return ResponseEntity.status(425)
        .body(new ErrorResponse("Too Early", ex.getMessage()));
}

// Return 425 Too Early
func errorHandler(w http.ResponseWriter, message string) {
	w.Header().Set("Content-Type", "application/json")
	w.WriteHeader(425)
	json.NewEncoder(w).Encode(map[string]any{
		"status":  425,
		"error":   "Too Early",
		"message": message,
	})
}

FAQ

What is the difference between 425 Too Early and similar status codes?

425 Too Early has specific semantics that distinguish it from other 4xx codes. Understanding these distinctions is crucial for proper API design and client error handling.

Should my API return 425 Too Early or a different status code?

Use 425 when the error precisely matches Too Early's definition. If the error is more general, consider 400 Bad Request. If it's about permissions, use 401/403. Always prefer the most specific status code that accurately describes the error.

How should clients handle 425 Too Early?

Clients should: (1) read the response body for error details, (2) determine if the error is retryable, (3) take corrective action if possible (fix input, refresh auth, wait and retry), (4) display an appropriate message to the user.

How does 425 Too Early affect monitoring and SLA calculations?

4xx errors are generally not counted against server-side SLAs since they indicate client errors. However, sudden spikes in 425 responses may indicate server-side issues (broken deployment, configuration change) even though they manifest as client errors.