When communicating via HTTP, a server is required to respond to a request, such as a web browser’s request for a web page, with a numeric response code and an optional, mandatory, or disallowed (based upon the status code) message.
In the code 404, the first digit indicates a client error, such as a mistyped Uniform Resource Locator (URL). The following two digits indicate the specific error encountered. HTTP’s use of three-digit codes is similar to the use of such codes in earlier protocols such as FTP and NNTP.
At the HTTP level, a 404 response code is followed by a human-readable “reason phrase”. The HTTP specification suggests the phrase “Not Found” and many web servers by default issue an HTML page that includes both the 404 code and the “Not Found” phrase.
A 404 error is often returned when pages have been moved or deleted. In the first case, a better response is to return a 301 Moved Permanently response, which can be configured in most server configuration files, or through URL rewriting; in the second case, a 410 Gone should be returned. Because these two options require special server configuration, most websites do not make use of them.
Yeah – deep in the weeds right, in short – you go to a webpage and it ain’t there no more !!!
Many 404 pages are boring, cryptic and ugly. Not the one for Nosh.me
The folks at Nosh build a mobile app (iPhone and Android) that is all about the foodie. Sharing images and recommendations of the food you eat and finding new dining choices from your social networks.
What Nosh also does well, seemingly better than many of the other food/dining-centric apps is to allow you to track your previous food adventures.
[shouts out to Wikipedia for the definition]
[image via Flickr]