| Previous | Next |
| HTTP_STATUS_CONFLICT | HTTP_STATUS_LENGTH_REQUIRED |
HTTP_STATUS_GONE
HTTP_STATUS_GONE represents HTTP 410 Gone. It tells the recipient that access to the target resource is no longer available at the origin server and that the condition is likely permanent. RFC 9110 recommends 404 Not Found instead when the server does not know whether the loss is permanent.
Why 410 is more specific than 404
A 410 response is useful when the server can deliberately communicate removal, such as a retired publication, deleted API object, or endpoint that has been permanently withdrawn without a replacement. It does not define an automatic redirect and does not tell a client where equivalent content moved. If a replacement URI exists, a redirect status with a Location field is usually the more descriptive protocol signal.
For diagnosis, verify that the application is intentionally selecting 410 rather than falling through a generic not-found handler. Also inspect cache behavior: 410 is heuristically cacheable unless the method definition or explicit cache controls say otherwise. A stale cached 410 can therefore outlive a backend repair if cache invalidation and response directives are wrong.
References
- RFC 9110, 410 Gone — permanence semantics and the distinction from 404.
- RFC 9111, HTTP Caching — cache processing relevant when a 410 response persists after an origin change.
Looking for a different code? Search another status or error code.