← Back to status codes
HTTP Status Code
410 Gone
Client ErrorThe requested resource is no longer available and is not expected to come back.
HTTP status code reference, response example, common causes, fixes, and related status codes.
What does HTTP 410 Gone mean?
HTTP 410 Gone is a status code sent by a server to indicate the result of an HTTP request.
Status codes help browsers, APIs, apps, and backend systems understand whether a request succeeded, failed, was redirected, or needs additional action.
In practice, HTTP 410 Gone usually appears when a server responds under specific request, validation, permission, or infrastructure conditions.
Response example
HTTP/1.1 410 Gone
HTTP example
HTTP/1.1 410 Gone
Common causes
- Resource permanently removed
- Endpoint deprecated and deleted
How to fix it
- Remove links to the resource
- Point clients to a replacement if one exists
Common mistakes
- Assuming the status code alone explains the full backend issue
- Ignoring related response headers that add important context
- Treating temporary errors as permanent failures
- Retrying too aggressively without checking the cause
- Debugging the frontend only when the problem is server-side
How browsers and APIs use it
Browsers, APIs, and backend services use HTTP status codes to understand the outcome of a request. Depending on the status code, an application may render content, retry a request, redirect the user, show an error, or trigger a different flow in the client or server.
Developer note
Use 410 instead of 404 when you want to clearly signal that a resource was intentionally removed.