Re: Premature end of script headers?

If I get this correctly you're running your CGI against Database #1 and it works fine from both the command line and the browser. Changing the CGI to run against Database #2 runs fine from the command line, but not from the browser. Is this correct? If that's the case, you should make sure that Database #2 is accessible from the user that your CGI is running as... that is, if it works from the command line then Database #2 is cool with you as the user... if it don't work from the browser then it seems clear to me that Database #2 has issues with the "web" user ("nobody" on many machines.)

Just a thought...

Gary Blackburn
Trained Killer

Comment on Re: Premature end of script headers?

Replies are listed 'Best First'.
Re: Re: Premature end of script headers? by MrCromeDome (Deacon) on Jun 21, 2001 at 22:22 UTC
You are exactly correct, except for one thing: even on the new database, the script does work from the browser with some parameters, but not with others. Regardless of the parameters passed though, the script entirely works from the command line. If the script didn't work from the command line, this would be pretty easy. But none of my die statements are ever reached. Nor does ActivePerl allow me to use CGI::Carp (at least not that I'm aware of).	[reply]

Replies are listed 'Best First'.

Re: Re: Premature end of script headers?
by MrCromeDome (Deacon) on Jun 21, 2001 at 22:22 UTC

does

If the script didn't work from the command line, this would be pretty easy. But none of my die statements are ever reached. Nor does ActivePerl allow me to use CGI::Carp (at least not that I'm aware of).

[reply]