In my experience it is most of the time related to an error being generated before the HTML-headers were completed.
Looking through the web-server error log might help. Adding "warningsToBrowser" could do no harm either. Making sure that you print the headers as soon as possible (CGI.pm header function) and disabling output caching is sometimes a solution.
CountZero
"If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law
In reply to Re: Premature end of script headers issue
by CountZero
in thread Premature end of script headers issue
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |