2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
set: 4
|
|
|
|
|
code: 410
|
|
|
|
|
title: Gone
|
2015-11-07 05:34:40 +01:00
|
|
|
references:
|
|
|
|
|
"Rails HTTP Status Symbol": ":gone"
|
2015-11-06 21:39:33 +01:00
|
|
|
---
|
|
|
|
|
|
2015-11-09 02:44:05 +01:00
|
|
|
The target resource is no longer available at the origin server and that this
|
|
|
|
|
condition is likely to be permanent.
|
2015-11-07 06:45:46 +01:00
|
|
|
|
|
|
|
|
If the origin server does not know, or has no facility to determine, whether or
|
2015-11-09 02:44:05 +01:00
|
|
|
not the condition is permanent, the status code [404 Not Found](/404) ought to
|
2015-11-07 06:45:46 +01:00
|
|
|
be used instead.
|
2015-11-07 05:34:40 +01:00
|
|
|
|
|
|
|
|
The 410 response is primarily intended to assist the task of web maintenance by
|
|
|
|
|
notifying the recipient that the resource is intentionally unavailable and that
|
|
|
|
|
the server owners desire that remote links to that resource be removed. Such an
|
|
|
|
|
event is common for limited-time, promotional services and for resources
|
|
|
|
|
belonging to individuals no longer associated with the origin server's site. It
|
|
|
|
|
is not necessary to mark all permanently unavailable resources as "gone" or to
|
|
|
|
|
keep the mark for any length of time -- that is left to the discretion of the
|
|
|
|
|
server owner.
|
|
|
|
|
|
|
|
|
|
A 410 response is cacheable by default; i.e., unless otherwise indicated by the
|
2015-11-09 02:44:05 +01:00
|
|
|
method definition or explicit cache controls<sup>[1](#ref-1)</sup>.
|
2015-11-07 05:34:40 +01:00
|
|
|
|
2015-11-09 02:44:05 +01:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
* <span id="ref-1"><sup>1</sup> Calculating Heuristic Freshness
|
|
|
|
|
[RFC7234 Section 4.2.2][2]</span>
|
|
|
|
|
* Source: [RFC7231 Section 6.5.9][1]
|
2015-11-07 05:34:40 +01:00
|
|
|
|
|
|
|
|
[1]: <http://tools.ietf.org/html/rfc7231#section-6.5.9>
|
|
|
|
|
[2]: <http://tools.ietf.org/html/rfc7234#section-4.2.2>
|
