Speaking from the 404.
Thursday, September 3rd, 2020
I was reading a little piece that covers the humble HTTP status code, the code that is returned when something goes wrong…or right in the process of transferring the stuff that makes up a web page from point A to point B.
200 OK
That’s the one that gets sent from the server when everything has gone just right, or right enough. There’s lots of them…
301 Moved Permanently 307 Temporary Redirect 401 Unauthorized 402 Payment Required 414 URI Too Long 500 Internal Server Error
And then there’s the one which shares a number with Atlanta’s longtime area code:
404 Not Found.
That means you’ve asked for a page and this server does not have anything at that address. The spec says you return ‘404’ and ‘Not Found.’ So many web-connected Atlantans grimace when they see gigantic ornate or elaborately animated 404s on websites which would like to entertain you in addition to supplying basic server information. We know exactly where the 404 is! You’re soaking in it.
But I guess this sort of cross-numerology could have different contexts if you lived in, say, Maryland, the 301 area code…moved permanently?
Or out in Wyoming…temporary redirect?
By the way, there is a site ‘devoted to the history of telephone service in the Atlanta, Georgia area.’ It’s a safe bet serving web pages via HTTP and HTTPS will not be covered at all.
