Nicholas,
Then get a book, or several. We don't read minds. We're glad to help if
there's something to look at. Arguing about it isn't going to solve your
problem. If you want a complete list of what causes "premature end of
script" headers, read "CGI Programming in Perl," "CGI Cookbook," anything
you can get your hands on about HTTP headers, the Apache documentation at
www.apache.org or Microsoft's IIS documentation, FTP'ing in ascii vs.
binary, and information about permissions on your operating system, to name
a few. If you don't give us anything to work with, you won't get anything
back. Having had plenty of experience getting that same error, I can tell
you that it's not the interpreter. I've spent entire days looking for the
cause of such an error and it has come down to things as simple as case
sensitivity or missing a semicolon on a HERE doc.
Your answer to "Is it in my script? Is it in my server config? Could it be
an error
in the PERL interperter?" is:
Maybe, maybe, and no.
Scot R.
inSite
-----Original Message-----
From: Nicholas Davey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 18, 2003 1:18 AM
To: Charles K. Clarkson; [EMAIL PROTECTED]
Subject: Re: Problem with script headers.
1 - I am a programmer, I have just never used PERL before.
2 - Why am I paranoid about my code?
First of all, I have parts of my code that are required to make the site
work properly.
Second, I have custom password checking code that I really dont want to
have to remove, seeing as how my site is 100% modular, and the pwd checking
code is used in each module I have.
Third, I just want to know what the heck could even be causing this
problem. Is it in my script? Is it in my server config? Could it be an error
in the PERL interperter?
The code syntax I am using is 100% valid, I am returning the proper HTML
headers/content-type(s), and I only have this problem with one file, which I
have deleted (shreaded) serveral times, re-written that one file, and still
get this error. It seems to me there is a problem with the script, not the
HTML output. Someone refered to fopen() being the problem. Its not. The
problem is with the interpeter not liking something in my script and
screwing up everything.
I just need a reason (or list of reasons) of what could be causing the
script to not even parse through the interperter and return and error like
"Premature end of script headers" which means the script isnt even running
fully before the problem arises.
www.vadtec.net
[EMAIL PROTECTED]
----- Original Message -----
From: "Charles K. Clarkson" <[EMAIL PROTECTED]>
Newsgroups: perl.beginners.cgi
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 18, 2003 12:57 AM
Subject: RE: Problem with script headers.
> Nicholas Davey <[EMAIL PROTECTED]> wrote:
> :
> : I hope I gave you enough info to maybe see
> : why index.cgi is the only freaking page that
> : doesnt work.
>
> IMO you have two choices.
>
> 1 - Hire a programmer to debug it and
> have her sign a confidentiality agreement.
>
> 2 - Post the code for index.cgi with the
> confidential parts changed such that
> it still generates the error.
>
>
> Telling us about the code and about how paranoid
> you are about your security won't aid us in solving
> your problem. Scot's right, we need the code.
>
>
>
> HTH,
>
> Charles K. Clarkson
> --
> Head Bottle Washer,
> Clarkson Energy Homes, Inc.
> Mobile Home Specialists
> 254 968-8328
>
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
