comment on

Please take the time to report the problem in its full form here. It's something you owe to the community.

Premature end of script headers can basically mean two things: that your script did not spit out anything, or that it printed something that cannot be considered an HTTP response.

You aren't telling us the whole story, anyway, because your code fragment starts with a comment about $data being already set up. Did you make sure that you actually reach that point? Are you sure your program isn't exiting before? Are you sure that you don't print anything on standard output before? What steps did you take to try and debug this?

Hey! Up to Dec 16, 2007 I was named frodo72, take note of the change! Flavio
perl -ple'$_=reverse' <<<ti.xittelop@oivalf

Io ho capito... ma tu che hai detto?

In reply to Re: Problem in data flow between a perl and a js file by polettix
in thread Problem in data flow between a perl and a js file by Nik

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.


Come for the quick hacks, stay for the epiphanies.
	PerlMonks