dirthurts wrote:
The short answer is that you called die before you sent the content-type header.
So your script is failing there, move the content header up and you will see the error message.
Anonymous Monk Ashley's question was about the internal server errors that
/s?he/ was receiving. The way that your reply to that question was worded,
"the short answer is....<snip>" and
"So your script is failing there" would suggest that the answer to the question is contained, succinctly, within your reply, when indeed it was not.
Furthermore, putting the content-type header before the die statement would have no effect on the output in this script, as Ashley was not outputting the die message to the browser, but to STDERR, which would be captured and written to the webserver's error log.
I, too, am concerned with pointing people in the right direction. I felt that your posts, if anything, would confuse the issue, aside from being technically incorrect.
higle
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.