HTTP 410 Gone

HTTP 410 Gone indicates the resource once existed at this URL but has been intentionally and permanently removed, with no forwarding address. Unlike 404 (which may be temporary), 410 is a definitive 'this content was deliberately deleted.' Search engines treat 410 more aggressively than 404 — they remove the URL from their index faster. Use 410 for content takedowns, expired promotions, and deleted user accounts.

Debug HTTP 410 live
Analyze real 410 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/410

Example request:

curl -i "https://httpstatus.com/api/status/410"
Try in playground

Meaning

The resource is no longer available and will not be available again (permanent). Unlike 404, 410 indicates the resource's absence is intentional and permanent.

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 410 Gone 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 410 Gone 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 410
A well-designed API returns 410 Gone 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 410
A web application receives 410 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 410
An observability system tracks 410 Gone responses. Client errors (4xx) are typically logged at WARN level since they indicate client issues, not server problems. Spikes in 410 responses may indicate a broken client deployment or API contract change.

Framework behavior

Express.js (Node)
Express: res.status(410).json({ error: 'Gone', message: 'Descriptive error' }). Custom error middleware: app.use((err, req, res, next) => { if (err.status === 410) res.status(410).json(err.body); });
Django / DRF (Python)
Django REST Framework handles 410 through exception classes. Custom: raise APIException(detail='Error message', code=410). DRF's exception_handler formats consistent error responses.
Spring Boot (Java)
Spring: throw new ResponseStatusException(HttpStatus.valueOf(410), "Error message"). Or use @ControllerAdvice to handle specific exception types and return 410 with structured error bodies.
FastAPI (Python)
FastAPI: raise HTTPException(status_code=410, detail='Error message'). Custom exception handler: @app.exception_handler(CustomError) to return 410 with structured error responses.

Debugging guide

  1. Read the full response body — well-designed APIs include error details explaining why 410 was returned
  2. Check request headers (Authorization, Content-Type, Accept) — many 410 errors stem from missing or incorrect headers
  3. Compare your request against the API documentation — verify required fields, parameter types, and URL format
  4. Use curl -v or httpie to reproduce the request and see the full HTTP exchange
  5. 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 410 Gone in Express
app.use((err, req, res, next) => {
  if (err.status === 410) {
    return res.status(410).json({
      type: 'https://api.example.com/errors/gone',
      title: 'Gone',
      status: 410,
      detail: err.message
    });
  }
  next(err);
});
Python
from fastapi import HTTPException

# Raise 410 Gone
raise HTTPException(
    status_code=410,
    detail={
        'type': 'gone',
        'message': 'Descriptive error for 410 Gone'
    }
)
Java (Spring)
// Spring Boot 410 Gone handling
@ExceptionHandler(CustomGoneException.class)
public ResponseEntity<ErrorResponse> handleGone(
        CustomGoneException ex) {
    return ResponseEntity.status(410)
        .body(new ErrorResponse("Gone", ex.getMessage()));
}
Go
// Return 410 Gone
func errorHandler(w http.ResponseWriter, message string) {
	w.Header().Set("Content-Type", "application/json")
	w.WriteHeader(410)
	json.NewEncoder(w).Encode(map[string]any{
		"status":  410,
		"error":   "Gone",
		"message": message,
	})
}

FAQ

What is the difference between 410 Gone and similar status codes?
410 Gone 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 410 Gone or a different status code?
Use 410 when the error precisely matches Gone'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 410 Gone?
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 410 Gone affect monitoring and SLA calculations?
4xx errors are generally not counted against server-side SLAs since they indicate client errors. However, sudden spikes in 410 responses may indicate server-side issues (broken deployment, configuration change) even though they manifest as client errors.

Client expectation contract

Client can assume
  • The request failed due to client-side inputs or policy.
Client must NOT assume
  • Retries without changes will succeed.
Retry behavior
Do not retry until the request is corrected (or credentials refreshed).
Monitoring classification
Client error
Use payload and header checks to avoid false positives; cacheability depends on Cache-Control/ETag/Vary.

Related status codes

409 Conflict
The request could not be processed because of conflict in the request.
411 Length Required
The request did not specify the length of its content.

Explore more

Related guides