HTTP Error 410 Gone

Introduction

The Web server (running the Web site) thinks that the URL requested by the client (e.g. your Web browser or our CheckUpDown robot) is no longer available from that system. This is not a 'never heard of it' response, but a 'does not live here any more' response.

The 410 error also indicates that the Web server has no forwarding address for the URL, so can provide no redirection to the new Web server. This condition should generally be considered permanent. If the Web server does not know, or has no way of knowing, whether or not the condition is permanent, the status code 404 - Not found should be used instead.

The 410 error is primarily intended to assist the task of Web maintenance by notifying the client system that the resource is intentionally unavailable and that the Web server wants remote links to the URL to be removed. Such an event is common for URLs which are effectively dead i.e. were deliberately time-limited or simply orphaned. The Web server has complete discretion as to how long it provides the 410 error before switching to another error such as 404. (Last updated: March 2012).

Fixing 410 errors - general

The Web server does have some record of the requested URL, but now believes that this URL should be serviced by a different Web server. The 410 error indicates a complete dead-end. The URL is effectively useless, and there is no clue as to an alternative Web server or URL which might be used instead.

If the URL really should be alive, then there is something fundamentally wrong with the setup of the Web server. You should see a similar 'not found' message when you try to access the site using any Web browser. Refer this to the Webmaster of the Web site.

Fixing 410 errors - CheckUpDown

Our service monitors your site for HTTP errors like 410. If the URL is genuinely dead, we may have to suspend your CheckUpDown account so that we do not waste Internet resources.


410 errors in the HTTP cycle

Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:

(1) Obtain an IP address from the IP name of the site (the site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
(2) Open an IP socket connection to that IP address.
(3) Write an HTTP data stream through that socket.
(4) Receive an HTTP data stream back from the Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '410'.


English 中文 Español Português Deutsch


Our company also owns these other Web sites:

A simple guide to software escrow.

Our really simple guide to web hosting (getting your web site and email addresses on the Internet using your own domain name).

Convert text to image file (GIF, JPG, PNG etc.) Free to use.

Tips if you want to buy a valuable Internet domain name.

Computer software and consultancy for Microsoft Windows and IBM AS/400 platforms. Utility and application software written in a variety of programming languages - particularly Java. Many free software offerings.

Our top-level company site.

 
Advertise on this site