News for hackers. Stuff that matters.
Re:The HTTP status code for a web server's default “hello” f... by panzi on Sunday July 09, 2023 @12:53PM (#36656135)
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.
Re:The HTTP status code for a web server's default “hello” f... by eli on Sunday July 09, 2023 @01:25PM (#36656512)
404 is the temporary code. 410 is permanent.
Re:The HTTP status code for a web server's default “hello” f... by pixl97 on Sunday July 09, 2023 @02:05PM (#36657090)
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.
Re:The HTTP status code for a web server's default “hello” f... by torgard on Sunday July 09, 2023 @04:40PM (#36658639)
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.