Hello,
I have Perl/CGI script that work fine but for the fact that it logs a
message in the error log file. The message is:
Use of uninitialized value in concatenation (.) or string at...
Despite the message, the script does what it is supposed to do. I would
like to know if this message is a
- Original Message -
From: Akbar Ehsan [EMAIL PROTECTED]
To: beginners-cgi@perl.org
Sent: Tuesday, February 06, 2007 9:26 AM
Subject: Trying to Understand An Error Message
Hello,
I have Perl/CGI script that work fine but for the fact that it logs a
message in the error log file
to Understand An Error Message
- Original Message -
From: Akbar Ehsan [EMAIL PROTECTED]
To: beginners-cgi@perl.org
Sent: Tuesday, February 06, 2007 9:26 AM
Subject: Trying to Understand An Error Message
Hello,
I have Perl/CGI script that work fine but for the fact that it logs a
message
Hi all,
I have received the respond from the Apache stated that:
The server encountered an internal error and was unable to complete your request.
Error message:
Premature end of script headers: testing.cgi
If you think this is a server error, please contact the webmaster.
Please help me
from the Apache stated that:
The server encountered an internal error and was unable to complete your
request.
Error message:
Premature end of script headers: testing.cgi
If you think this is a server error, please contact the webmaster.
Please help me to solve this problem.
PS
Hi all,
I have received the respond from the Apache stated that:
The server encountered an internal error and was unable to complete
your request.
Error message:
Premature end of script headers: testing.cgi
If you think this is a server error, please contact the webmaster
Not really. If your form allows uploads, your form allows uploads. That's
where DoS comes into play. Disguising the location of your code is a start,
but you still have to figure out what you're going to do if someone tries to
paste rogue code into your form or hit you with an obnoxiously large
The answer to your question is: Be afraid, be very afraid. A wiley cracker
may be able to run system commands if you allow him/her to upload code.
Even
without knowing that much, they could simply create a script that
generates
a big enough upload to cause DoS (denial of service) on your
will exit cleanly with an error message.
The answer to your question is: Be afraid, be very afraid. A wiley cracker
may be able to run system commands if you allow him/her to upload code. Even
without knowing that much, they could simply create a script that generates
a big enough upload to cause DoS
: http://teddy.fcc.ro/
Email: [EMAIL PROTECTED]
- Original Message -
From: Scot Robnett [EMAIL PROTECTED]
To: Cool Hand Luke [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Monday, March 31, 2003 10:57 PM
Subject: RE: The very un-useful 'premature end of script headers' error
message
I was out
]
Sent: Friday, March 28, 2003 5:44 PM
Subject: Re: The very un-useful 'premature end of script headers' error
message
Cool == Cool Hand Luke [EMAIL PROTECTED] writes:
Cool Hello All,
Cool I think I figured it out, (so far). I 'm pretty sure that it
has to do
Cool with perl 5.003 disliking
script will be found in the error log. Until you
can
see those logs, we're just guessing.
Hi just thought I'd let y'all know I've figured out how to get more
effective error messages. I decided to start from scratch with the
original
sample script I postedhere's my error message now
:44 PM
To: [EMAIL PROTECTED]; Cool Hand Luke
Subject: Re: The very un-useful 'premature end of script headers' error
message
Cool == Cool Hand Luke [EMAIL PROTECTED] writes:
Cool Hello All,
Cool I think I figured it out, (so far). I 'm pretty sure that it has
to do
Cool with perl 5.003
, but not your expertise.
-Original Message-
From: Randal L. Schwartz [mailto:[EMAIL PROTECTED]
Sent: Friday, March 28, 2003 9:29 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Cool Hand Luke
Subject: Re: The very un-useful 'premature end of script headers' error
message
Bill == Bill Burke
Vegetables?'),
... snip ...
it works. Otherwise you get a Undefined subroutine
main::caption called at
... error message.
Is there an explanation for this?
CGI.pm has two different styles, looks like you're
mixing them. Basically, you've got your standard
function style:
use CGI qw/:standard
a Undefined subroutine main::caption called at
... error message. You'll get the error as soon as yo include the
caption-line or if you just write th(... (also td + Tr) instead of
$q-th(...
Is there an explanation for this?
Richard
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Richard Krause [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Hi all
(...)
#td(['Broccoli' , 'no', 'no', 'yes']),
#td(['Onions' , 'yes','yes', 'yes'])
#]
#)
missing a comma ^
Richard,
You did take that from the 'Rat' book, but in the book
use CGI qw( standard );
Allows the author to use an implicit $q- so he can write table
where as you need to write $q-table, $q-Tr, $q-td etc.
HTH
Richard Krause [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]">news:[EMAIL
Can anyone explain what this error message is trying to tell me ...
[03/Jul/2001:17:31:08] catastrophe (20762): for host ... trying to GET
/ITP_Billing/cgi-bin/Library/JavaScripts/misc_services_menu.js,
cgieng_start_ou
tput reports: could not fork new process (exec() failure [Exec format
error
-
- Original Message -
From: Sally [EMAIL PROTECTED]
To: perlcgi [EMAIL PROTECTED]
Sent: Tuesday, June 12, 2001 2:34 PM
Subject: error message
Anyone know what this means:
Premature end of script headers:
I found it in my server error log, after I got an internal server error
message when
Anyone know what this means:
Premature end of script headers:
I found it in my server error log, after I got an internal server error
message when I tried to look at a new page I'd created.
know what this means:
Premature end of script headers:
I found it in my server error log, after I got an internal server
error message when I tried to look at a new page I'd created.
--
Gary Stainburn
This email does not contain private or confidential material as it
may be snooped
Gary Stainburn wrote:
This is what you get when you run a CGI and the cgi terminated before
generating any valid output. Usually this happens if the perl script
doesn't compile and therefore doesn't run.
try 'perl -c script' to see if it compiles okay
if your script compiles without
Try putting the following at the beginning of your script, it helps a lot
with debugging CGI:
use CGI::Carp qw/fatalsToBrowser/;
Instead of getting the usual Internal Server error, it displays the error in
your browser. Of course, make sure you have CGI first.
Or maybe you could write a simple sub that catches any anomolies at run time and
produces an Error message of your choosing. There is a good example of this in Chap. 5
of CGI Programming with Perl. You can also find the example from the chapter here:
http://examples.oreilly.com/cgi2/
Good
25 matches
Mail list logo
