A rule for user interaction: keep debugging information out of error messages
Yet another example of bad web programming. I was researching the subject of cancer and followed a link on a government site that gets me to this page:
I think its fine to print debugging information to the screen when a website is under development, but on a live site, I think the error messages should try to be more helpful. Perhaps the error message can suggest the average speed it takes the site’s sysadmins to fix problems of this time. Or the error message can suggest that the visitor go get the page out of the Google cache. Even the cutesy error message that Stikipad used was more reassuring than this.