|
You are here |
greenbytes.de | ||
| | | | |
www.schakko.de
|
|
| | | | | ||
| | | | |
www.gamerdad.com
|
|
| | | | | Video game news, views, & reviews from a parental perspective, presented by Andrew S. Bub - The GamerDad | |
| | | | |
mathieu.fenniak.net
|
|
| | | | | A time-traveler is passing by 2013 and she opens a browser bookmark to http://mars.gov/blog/**2056**/11/21/news.html. What HTTP status code does she get back from her response? Well, it's not going to be 200 OK, because it wasn't OK with the server. The server couldn't find the article that the client requested, because it won't be published for another 43 years. "Couldn't find the article" sounds like a 404 Not Found status code. OK, very reasonable choice. But, "The server couldn't find the article" raises a bit of a doubt. A 404 is part of the 4xx-series status codes, which are all for client errors. Was this a client error, if it was the server's fault for not finding the article? Shouldn't she be getting 5xx Not Found? | |
| | | | |
nabeelvalley.co.za
|
|
| | | Debug Node.js code using your browser's dev tools | ||