Whenever you get a 500 error, first step I would recommend
in your debug procedure is to run it from the command line.
Most times a an error will pop up right there. What you want
to check for is something (like an error message) being printed
before your header (speaking of which we can't see your code
that is printing you headers, so I can't comment on how you
are printing your headers, which could be another problem).
Second step would be to check the log files for an error
message. This might clue you into a permission problem.
If you do those 2 steps there isn't usually a step 3 :)
couple comments on your code:
You are calling in all the CGI methods into your
namespace (use CGI ':standard') but then you
use the Object interface.
You do a 'use vars qw($baseURL);' when (I'm
guessing) you only need a lexical scoped to the main package
'my $baseURL;'
grep
|
Unix - where you can throw the manual on the keyboard and get a command |
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.