Follow this easy sequence of steps:

1. Make sure this works:

   #!/bin/sh
   echo content-type: text/plain
   echo
   date
   [download]

   (If you're not on Unix, you can skip this step, but this reveals a lot about the CGI setup without having to introduce the unknown of Perl.)
2. Make sure this works:

   #!/your/path/to/perl
   print "Content-type: text/plain\n\n";
   print "Hello world at " . localtime() . "\n";
   [download]

3. Now take your original script, and insert these right after the #! line:

   #!/your/path/to/perl
   BEGIN { print "Content-type: text/plain\n\n--OUTPUT--\n"; }
   ... rest of your script ...
   [download]

   and make sure your code passes perl -c.

You should now see as the first few lines of output the exact headers and body sent by your program to the server. If the first lines up to the blank line are not nicely formatted headers, fix your script as needed. Once the headers are fixed, you can remove the BEGIN block.

Also, every time you see that sort of error, a sometimes-useful error message has been written to your web server's error log, so find that as well. If you don't have access to the server log, a simple fix is to change step three's suggestion to:

BEGIN {
  print "Content-type: text/plain\n\n--OUTPUT--\n";
  open STDERR, ">&STDOUT"; # errors go to browser now
}
... rest of your script ...
[download]

And now the error messages show up in your browser, as if your browser was the result of invoking the script as a command line.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.