/explore
|
You are here 
|
greenbytes.de | ||
| | | | |
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? |
|
| | | | | ||
| | | | |
nullprogram.com
[AI summary] A developer explains why the Atom web feed specification is superior to the flawed and ambiguous RSS standard while discussing their experience building a feed client. |
|
| | | | | ||
| | | | |
www.schakko.de
|
|
| | | | | ||
| | | | |
mths.be
[AI summary] An article explains how the 'u' and 'y' regular expression flags affect Unicode handling in ECMAScript 2015, covering syntax changes, quantifier behavior, and compatibility issues. |
|
| | | |||
