The (not so helpful) but secure, "url was not found on this server" error
Posted: Thu Jun 01, 2006 7:41 pm
I've been getting the 404 error intermittently with my current install (.13) Granted, I moved to a new webhost at the same time I upgraded to .13, so I"m not entirely sure it's due to the .13 upgrade.
The hosting provider assures me that nothing strange is happening on the server, ie, database connectivity is up, plus, other mysql based websites are working on the same domain...
To try to diagnose, I turned on the debug flag in config.php, however, this didn't provide me any more information, still got:
Not Found
The requested URL was not found on this server
I was hoping this flag would cause a mysql error message or something like that to be printed.
Since it didn't, I added a line of code to send myself an email (with the mysql_error() in the body of the mail), and I'm now just waiting for it to happen again.
Anyone have any suggestions on what could be causing the 404? I plan to look into the code more closely, but I know for sure that db errors can cause it, since I set the wrong db password in the config file and it happened.
Also, a suggestion: maybe the code could be changed to send email to the admin of the CMS if ever a 404 error is returned to a browser, or maybe write a log file somewhere. I understand the desire to hide mysql errors, but there should still be a way for an admin to see the cause of the problem.
Thanks,
Wes
The hosting provider assures me that nothing strange is happening on the server, ie, database connectivity is up, plus, other mysql based websites are working on the same domain...
To try to diagnose, I turned on the debug flag in config.php, however, this didn't provide me any more information, still got:
Not Found
The requested URL was not found on this server
I was hoping this flag would cause a mysql error message or something like that to be printed.
Since it didn't, I added a line of code to send myself an email (with the mysql_error() in the body of the mail), and I'm now just waiting for it to happen again.
Anyone have any suggestions on what could be causing the 404? I plan to look into the code more closely, but I know for sure that db errors can cause it, since I set the wrong db password in the config file and it happened.
Also, a suggestion: maybe the code could be changed to send email to the admin of the CMS if ever a 404 error is returned to a browser, or maybe write a log file somewhere. I understand the desire to hide mysql errors, but there should still be a way for an admin to see the cause of the problem.
Thanks,
Wes