Explore >> Select a destination
|
You are here 
|
alexrichey.com | ||
| | | | |
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... | |
| | | | |
ewintr.nl
|
|
| | | | | ||
| | | | |
aarol.dev
|
|
| | | | | Anyone who has implemented a simple HTTP 1.1 server can tell you that it is a really simple protocol. Basically, it's a text file that has some specific ... | |
| | | | |
www.redotheweb.com
|
|
| | | As we're reinventing web applications with SPAs and frontend frameworks, we need to reinvent web application security, too. | ||
