/explore
|
You are here 
|
alexrichey.com | ||
| | | | |
linksort.com
|
|
| | | | | In writing a REST API, we have to deal with at least two types of errors. Client errors: These errors are the fault of the user, e.g., providing an invalid... | |
| | | | |
blog.carlana.net
|
|
| | | | | The other day, I was reading a website about some historical documents, when I saw that it had an error message on top: Screenshot from the site Some quick searching online for the error message revealed that it was caused by a mismatch between the site's versions of PHP and WordPress. Older versions of WordPress had a bug in the switch statement of a certain localization component, and later versions of PHP dump a warning about this bug out to the end user HTML. When I came back to the site a few days later, it had been fixed. The ultimate reason for my seeing for the error message as a random reader is that PHP has too many ways to deal with errors: Builtin PHP functions, and therefore any PHP project, have a whole range of error handling mechanisms - erro... | |
| | | | |
lanre.wtf
|
|
| | | | | Errors in http handlers in Go are ridiculously complex to handler. Depending on how simple or complex your handler is, you can always fail to return an error somewhere after sending the response. Here is how I handle it | |
| | | | |
lewisdale.dev
|
|
| | | Now it's time to actually try and send a "ping" to a website | ||
