HTTP codes are defined by standard, 404 always being interpreted by standards-compliant clients as "not found". The technically correct codes would be HTTP 400 or HTTP 500. But neither of those are as iconic or funny (or recognizable for non-web nerds) as 404. /endpedantry
HTTP codes are defined by standard, 404 always being interpreted by standards-compliant clients as "not found". The technically correct codes would be HTTP 400 or HTTP 500. But neither of those are as iconic or funny (or recognizable for non-web nerds) as 404. /endpedantry
It's not (just) the client, you could/can define a custom error page on the server, which would be served if the server generated a 404.
HTTP codes are defined by standard, 404 always being interpreted by standards-compliant clients as "not found". The technically correct codes would be HTTP 400 or HTTP 500. But neither of those are as iconic or funny (or recognizable for non-web nerds) as 404. /endpedantry
It's quite simple really The joke won't work otherwise