I have a couple of suggestions for debugging -

Since you have warnings enabled and use strict;, let perl help you even more -
use CGI::Carp qw/fatalsToBrowser/; while debugging the script (remove it in production). The server logs should have the actual error message as well.

If that doesn't make things jump out at you, look here for a good troubleshooting guide.

Lastly, you might try typing 'premature end of script headers' into the search box at the top of the page. Believe it or not, it's been discussed here before ;-)

In reply to Re: Strange problem on upgrading Perl and CGI by jsprat
in thread Strange problem on upgrading Perl and CGI by michellem

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.