in reply to Premature end of script headers

Since you print a minimal http header, followed by an immediate redirect to some other page, I'd look on that other page, because your browser is going there and not coming back (because that's what you told it to do). GETVALUES will never recieve anything all from the browser.

You would also want to see what is in your error_log just before the "Premature end of script headers" message.

Finally, use CGI or comse other module to properly parse the query (when you actually receive one).

--Bob Niederman, http://bob-n.com

Replies are listed 'Best First'.
Re: Re: Premature end of script headers
by Nickd_69 (Novice) on Aug 01, 2003 at 05:15 UTC
    Hey bob. Thanks for your comments. The premature end of script headers is the last thing in my log. There are no others. Any other ideas?

      There are no ther entries in the error_log? that is strange

      Other posters have had great suggestions coming down to

      1. use "\r\n" instead of "\n" when sending headers (though my testing doesn't indicate that this is the problem, YMMV)

      2. turn on warnings with -w in the #! line or use warnings; in the script.

      3. run this from the command line and see what happens, possibly finding some way to feed it the values it wants. At least run as perl -cw scriptname which will find compile time errors.

      4. use CGI; to rpint the redirection (probably without the headers, as others have noted here,

      --Bob Niederman, http://bob-n.com