I think it's important to differentiate between the
different types of errors that you're handling. For errors
that are caused by invalid user input, it's a good idea
to create an error page that tells them what to correct in
their input - probably including the current input you've
got and pointing out what needs to be fixed.
For anything that is outside of the user's control
(missing files on the server, invalid permissions, that
kind of thing) I think that it's a waste of time creating
clever error reporting pages. You're probably not going to
give the user any information that will mean anything to
him than the default web server error page and you run the risk of giving a passing cracker too much information.
The "vanilla" 500 Error page is fine for most purposes. Of course, there's nothing to stop you replacing it with another that better reflects the look and feel of your site.
"The first rule of Perl club is you do not talk about
-- Chip Salzenberg
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||