HTTP 410 Gone — What It Means and How to Fix It

The HTTP 410 Gone status code indicates that the target resource is no longer available at the origin server and that this condition is likely to be permanent. Clients should not expect the resource to return and should remove any cached links to it. This code is more definitive than a 404 Not Found, implying a deliberate and permanent removal.

Last updated: 2026-06-11

RECOMMENDED

Essential Reading: Designing Data-Intensive Applications

The system design bible for software engineers. Learn to build reliable, scalable, and maintainable systems.

View on Amazon →

                Status Code
                410
            

Name Gone

Common Causes

The resource (e.g., a specific product page, an old API endpoint, a user profile) has been intentionally and permanently deleted.
A content management system (CMS) or application has marked content as 'gone' rather than just 'not found'.
An old version of an API or a specific API resource has been deprecated and removed without a redirect.

Code Examples to Handle HTTP 410

curl -I https://httpbin.org/status/410

fetch('https://httpbin.org/status/410')
  .then(response => {
    if (response.status === 410) {
      console.log('Handled Gone');
    }
  });

import requests

response = requests.get('https://httpbin.org/status/410')
if response.status_code == 410:
    print("Received Gone")

How to Fix It

**Verify Resource Status:** Confirm with the server administrator or content owner that the resource was indeed permanently removed. This is crucial as a 410 implies intent.
**Update Client References:** If the resource is truly gone, update any client-side links, bookmarks, or application code that references the old URL to remove them or point to an appropriate alternative (e.g., a new version, a category page, or the homepage).
**Check Server Configuration:** For server owners, review your server's configuration (e.g., web server rules, application logic) to ensure 410s are only issued for resources that are permanently unavailable and not due to misconfiguration or temporary issues.

💡 Example: A popular e-commerce website decides to discontinue a specific product line. Instead of returning a 404 for the old product pages, they configure their server to return a 410 Gone, signaling to search engines and users that these products will never be available again, prompting them to remove the links from their indexes and bookmarks.

🛠️ Developer Tip: When issuing a 410, ensure it's a deliberate decision for permanent removal. For temporary unavailability or if the resource might return, a 404 or 403 might be more appropriate. Consider including a 'Date' header indicating when the resource was removed.

Related Status Codes

Frequently Asked Questions

What causes HTTP 410?

HTTP 410 is caused when a server intentionally and permanently removes a resource. It signifies that the resource will not be available again at that URL, unlike a 404 which suggests the resource might be temporarily missing or the URL is incorrect.

How do I fix HTTP 410?

As a client, you 'fix' a 410 by removing any references to the gone resource. As a server owner, ensure you only issue 410s for truly permanently removed content and consider providing alternative resources or a clear message on a custom 410 page.