This warning also appears with any scalar constant created with
constant.pm -- pretty darn annoying for cgi error_logs. Is there
a more 'official' fix or suggestion why mod_perl triggers this?
-j
On Tue, Jun 20, 2000 at 02:06:00PM +0100, Martin Wood wrote:
Thanks for the info. - mv warnings
Part of the problem I've had is transitioning a cgi application onto
mod_perl and keeping performance up on both platforms until a switch
can be made. So I've done some comparisons of the various dbh schemes.
Comments and corrections very welcome. I'm wary of connect_cached()
under mod_perl but
I am a bad hacker and watching your line. I see cookies A and B go to you.
I set cookies A and B in my web browser. I am now you. You can try to
permute the cookies with IP# (breaks on proxies) or Browser type, but all
cookie based approaches believe in the value of something sent cleartext.
perl Makefile.PL USE_APACI=1 EVERYTHING=1 APACHE_PREFIX=/usr/local/apache
On Thu, Jan 20, 2000 at 03:36:44PM -0600, Wang, Pin-Chieh wrote:
Hi,
I am building mod_perl-1.21 into apache_1.3.9 using apaci.
I run the following commands under mod_perl-1.21 directory
perl Makefile.PL EVERYTHING=1
Sorry if this seems perl and not mod_perl, but its from the
mod_perl book n all. On page 115, in Lincoln's navbar code
he writes a loop as:
local $/ = "";
while ($fh) {
s:(/BODY):$navbar$1:i;
s:(BODY.*?):$1$navbar:i;
} continue {
Does anyone have experience using an alarm() call under Apache::Registry?
Should I set alarm(0) as my script "exits" or is it ok to leave it set?
I'm using it to cap runaway scripts.
-j
