AHHHH (25 of 26)
FUCK INTERNAL SERVER ERRORS.
WORST. ERROR MESSAGE. EVER.
“This is a ‘catch-all’ error generated [from the] Web server. […] something has gone wrong, but the server can not be more specific about the error condition in its response to the client. In addition to the 500 error notified back to the client, the Web server should generate some kind of internal error log which gives more details of what went wrong. It is up to the operators of [the] Web server site to locate and [review] these logs.” [source]
I don’t have access to those logs at work, which makes debugging the code I wrote lots of fun. The method of debugging that I am stuck using is:
- Comment out the last line of non-commented server-side code in the file.
- Reload page and see if an internal server error still exists.
- Repeat as needed.
Another fun fact is that since the project I am working on is for the Intranet, it means that I can’t tell someone who might hire me to go there and see an example of work I’ve done.
No worries, cause in two weeks I’m back to TPRS full-time (read full-time as in addition to school).
