Skip to main content
Warning This document has not been updated for a while now. It may be out of date.
Last updated: 9 Jun 2020

content-store: # Gone items

Gone items

To represent content that is no longer available, the content store will support items with a format of "gone". These will cause a gone route to be setup in the router so that the item returns a 410 HTTP status.

Items with a format of gone will have all routes setup in the same way as other item types (described in route_registration.md), with the exception that instead of routing to the rendering_app, routes will be created as gone routes.

For example, given the following request:

PUT /content/gone-foo
{
  "format": "gone",
  "publishing_app": "publisher",
  "routes": [
    {"path": "/gone-foo", "type": "exact"},
    {"path": "/gone-foo/bar", "type": "exact"}
  ]
}

The following route would be created:

/gone-foo (exact) => gone
/gone-foo/bar (exact) => gone