in reply to What could prompt an internal server error?

Been there. Frustrating.

One of the following should be helpful:
   a)Running the script from the command line.
   b)Checking the server error log.

Update:
Following crazyinsomniac's suggestion here's a slightly different take on some good stuff to include near the top of your script

use CGI::Carp; use CGI::Carp qw(fatalsToBrowser); local $SIG{__WARN__} = \&Carp::cluck;

Replies are listed 'Best First'.
Re: Re: What could prompt an i.s.e.?
by Anonymous Monk on Jun 05, 2001 at 10:23 UTC
    I'm using fatalsToBrowser already.
      But what about suggestions a) and b)?

      Perhaps my "should be helpful" was a little too casual. Those are not throw-away suggestions. They are likely the two most common and effective strategies for solving the kind of problem you describe. If you peruse the archives here at Perl Monks you will see them recommended again and again.

      They will likely lead you to a solution to your current problem. And checking those two things should become second nature for you any time you have a problem of this sort because they are such reliable strategies.

      In particular, find out where your server error log is and befriend it. It is one of your most reliable resources for debugging CGI.

Re: Re: What could prompt an i.s.e.?
by Anonymous Monk on Jun 05, 2001 at 09:14 UTC
    Try "Content-Type: text/html\n\n";
    Note capital 'T' for 'Type'. Good luck.
      Apache (on both Linux and Windows) is happy to accept each of the following:
      Content-type: text/html Content-Type: text/html CoNtEnT-TyPe: text/html
      The original poster does not mention which server is being used. I can't find a definitive word on capitalization on HTTP headers but the HTTP docs I can lay my hands on seem rather casual about capitalization. YMMV