The woman dumped the contents of her purse onto the table before her, ignoring the odd glances she received from the people around her. Rummaging through her belongings, or so she assumed, her lips as low mutters escaped her; anxious and incoherent. There was nothing worse than feeling lost and like something was missing. Just who was she? What was her name? Where was she?
Picking up a folded newspaper from the pile, her eyes scanned the text, looking for any indication of where she was. So what if she was trembling and anxious? A huge part of her was missing, who could blame her?
Embracing HTTP error code 410 means embracing the impermanence of all things.
Mark Pilgrim, March 27, 2003
HTTP Status 410 Spec:
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a “404 Not Found” may be used instead.