Another approach to debugging a cgi is to run it from the command line. This assumes that you have shell access to the server you are debugging on. If you don't have shell access, to a production machine perhaps, set up another machine where you do have access that mimics the production machine.
To make this somewhat painless, put this into your code:
use CGI qw/ -debug/;
then run the cgi from the command line. At this point you'll get:
(offline mode: enter name=value pairs on standard input)
and you can type in the parameters ( foo=555 <return> and so on, followed by a <ctrl>D to end). If things aren't going well, you'll see the error messages in your shell. If you cgi spits out a badly formated response, you'll see that.
There are other tricks too, read more about it at:
CGI
Cheers
--Freddo411
-------------------------------------
Nothing is too wonderful to be true
-- Michael Faraday
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.