in reply to Premature end of script headers issue
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
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Premature end of script headers issue
by Anonymous Monk on Jan 10, 2005 at 21:07 UTC | |
by CountZero (Bishop) on Jan 10, 2005 at 21:13 UTC | |
by Anonymous Monk on Jan 10, 2005 at 21:18 UTC | |
by CountZero (Bishop) on Jan 10, 2005 at 21:35 UTC | |
by Anonymous Monk on Jan 10, 2005 at 21:48 UTC | |
|