Originally posted by dang65
View Post
implementationThe problem is that so many front-end coders (and indeed quite a few back-end ones) don't understand distributed applications. They never have an HTTP failure running on localhost, so they stick their code into the world without any HTTP error handling.
The first of the Eight Fallacies of Distributed Computing is "The network is reliable." Being victims of this fallacy, many of them don't even bother checking for an HTTP status code of 200 OK. Throw them a 500 Internal Server Error, and they'll attempt to stuff the error message into the <select>, which of course fails miserably.
And don't get me started on sites that return a page that says 404 Not Found but with an HTTP status of 200 OK

Leave a comment: