Hacker News Reader

Comment by mojuba | Hacker News Reader

That, and "Coming soon" shouldn't be remembered either. So why not have a e.g.

    205 Temporary Placeholder

or something along those lines?

View on HN

Ironically, I sought to make a reference to the GeoCities "Under Construction" animated GIFs, and upon visiting knowyourmeme.com, they served me a 500 error on their landing page. Justice!

Is that ultimately not the same as 404 – The resource you requested was not found, so here is a temporary placeholder?

Browsers, proxies and crawlers might remember 404 longer than any status code that has "temporary" in it. See also the various permanent and temporary redirect status codes.

404 is the temporary code. 410 is permanent.

Have you ever seen a 410 actually used IRL? This has to be one of those that's pretty high up in the code rarity list.

I've used it for resources that have been permanently deleted, rather than the 404 that you'll usually see. I think it makes sense for that sort of stuff.

From a user perspective, getting a 404 after following a link that previously worked can indicate a couple of things. Like maybe the resource still exists in some other place, but they didn't set up redirects. Maybe it's been "privated" in some way, and I no longer have access to it.

A 410 makes it explicitly clear to me, that the resource has been permanently deleted. It'd also be nice if the response included some metadata as to when the resource was deleted.

Reply on news.ycombinator.com