[wp-trac] [WordPress Trac] #21306: Archived blogs should return HTTP "404 Not Found", not "410 Gone"

[WordPress Trac]

#21306: Archived blogs should return HTTP "404 Not Found", not "410 Gone"
-----------------------------+------------------------------
 Reporter:  amattie          |       Owner:
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Multisite        |     Version:
 Severity:  normal           |  Resolution:
 Keywords:  has-patch close  |
-----------------------------+------------------------------
Changes (by jeremyfelt):

 * keywords:  has-patch => has-patch close


Comment:

 Also from the
 [http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.11 HTTP
 spec], describing intent:

 > 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 working at
 the 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.

 While I don't think 404 would be a bad thing in this scenario, I think 410
 still makes sense. See the [http://www.colorado.gov/error/410-GovRitter-
 archive.html former Colorado governor's archived site] as an example.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/21306#comment:1>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software