apache::status on win32
Hi with winXP Embedded Perl version v5.6.1 for Apache/1.3.26 (Win32) mod_perl/1.27_01-dev Apache Status is not working as expected the httpd.conf configuration is Perl Module Apache::Status (before any other module) PerlModule B::TerseSize location /perl-status SetHandler perl-script PerlHandler Apache::Status PerlSetVar StatusOptionsAll On PerlSetVar StatusTerseSizeMainSummary On Allow from localhost /location the memory usage link http://localhost:8080/perl-status? status_memory_usage produces an apache segfault in SIZE.dll (but apache does not die) http://localhost:8080/perl-status?inc returns ok but other links of the form below return FORBIDDEN : http://localhost:8080/perl- status/Apache::Constants::EXPORT/ARRAY?data_dump http://localhost:8080/perl- status/Apache::Request::bootstrap/FUNCTION?cv_dump Best Regards Pascal Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,13 /mn) ; tél : 08 92 68 13 50 (0,34/mn)
Re: Filehandles
Stas Bekman [EMAIL PROTECTED] writes: [...] perl 5.8.0 internals are thread-safe, so does mod_perl 2.0-dev. By saying that perl is thread-safe, I mean that operations like push, =, /, map, chimp, etc. are thread-safe. ^ A thread-safe chimp; amazing! Try doing *that* in Java. -- Joe Schaefer
problems installing libapreq-1.0
I have two identical hosts with the following mod_perl-1.26 apache apache_1.3.26 ben apachessl_1.48 openssll-0.9.6b on one, libapreq-1.0 installs just fine, on the other I get this error: In file included from /usr/lib/perl5/site_perl/i386-linux/auto/Apache/include/include/httpd.h:79, from apache_request.h:5, from apache_request.c:59: /usr/lib/perl5/site_perl/i386-linux/auto/Apache/include/include/buff.h:75: openssl/ssl.h: No such file or directory /usr/lib/perl5/site_perl/i386-linux/auto/Apache/include/include/buff.h:78: #error Don't use OpenSSL/SSLeay versions less than 0.9.2b, they have a serious security problem! make[1]: *** [apache_request.o] Error 1 I can't figure out what the problem is. all the include files appear to be in the same places on both machines. I've rebuilt everything from scratch on the machine that fails :-( Any ideas?? Michael
Re: problems installing libapreq-1.0
never mind. It appears that the order in which things are done is important. I finally got it to work by reinstalling mod-perl for the umpteenth time and then again trying libapreq. Strange, the old version that was installed would no re-install until I did this. I have two identical hosts with the following mod_perl-1.26 apache apache_1.3.26 ben apachessl_1.48 openssll-0.9.6b on one, libapreq-1.0 installs just fine, on the other I get this error: In file included from /usr/lib/perl5/site_perl/i386-linux/auto/Apache/include/include/http d.h:79, from apache_request.h:5, from apache_request.c:59: /usr/lib/perl5/site_perl/i386-linux/auto/Apache/include/include/buff .h:75: openssl/ssl.h: No such file or directory /usr/lib/perl5/site_perl/i386-linux/auto/Apache/include/include/buff .h:78: #error Don't use OpenSSL/SSLeay versions less than 0.9.2b, they have a serious security problem! make[1]: *** [apache_request.o] Error 1 I can't figure out what the problem is. all the include files appear to be in the same places on both machines. I've rebuilt everything from scratch on the machine that fails :-( Any ideas??
Apache::PerlRun weird behavior?
Hi I'm new at mod_perl, and I decided to start running my scripts with
Apache::PerlRun so I don't have to rewrite them right away (they're too
'dirty' to run under Apache::Registry). Anyway, I figured it was going
to be easy since PerlRun provides an environment similar to CGI, but
something strange is happening. There's a section in the User Guide that
talks about possible problems one can encounter with referenced
variables, so I figured I'd write a very simple test script to see if
that was the case with my code.
So the weird thing is that it runs fine the first time, but when I
reload the page, it doesn't show the variable I imported from
My::Config, and this is what the output looks like this:
html_dir =
count = 1
And this message shows up in the error.log:
[Sat Aug 31 19:59:15 2002] test.pl: Use of uninitialized value at
/home/val/www/cgi-bin/test.pl line 12.
This is such a simple script, but I can't figure out what I'm doing
wrong. What's even more weird is that if I change my httpd.conf to use
Apache::Registry instead of Apache::PerlRun, the script works fine!
(well the value of $count keeps incrementing, but I expected that).
Could someone please tell me what I'm doing wrong? My settings/code are
shown below:
- httpd.conf -
PerlWarn On
PerlTaintCheck On
PerlModule CGI
Alias /cgi-perl/ /home/val/www/cgi-bin/
Location /cgi-perl
SetHandler perl-script
PerlHandler Apache::PerlRun
Options +ExecCGI
allow from all
/Location
- test.pl -
#!/usr/bin/perl -w
use strict;
use CGI;
use My::Config;
use vars qw($count);
my $q = new CGI;
$count++;
print $q-header(-type='text/html');
print html_dir = $CF{'html_dir'}br;
print count = $countbr;
- My/Config.pm -
package My::Config;
use strict;
use Exporter;
use vars qw(ISA EXPORT %CF);
ISA = ('Exporter');
EXPORT = qw(%CF);
$CF{'html_dir'} = '/home/val/www/htdocs';
1;
$r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn't work
Hi all,
I'm sure I'm just missing something, but I'm stumped.
I've got an access handler that does some tests and then conditionaly does this:
$r-push_handlers('PerlAuthenHandler', 'Some::handler');
return OK;
Some::handler() starts by printing the current callback to the error log, which never
happens if it's set to run in the 'PerlAuthenHandler'. If I change the push_handlers()
to use 'PerlFixupHandler', then Some::handler() gets called and I see it in the error
log.
What am I doing wrong? I know it has to be me.
---
Rodney Broom
President, R.Broom Consulting
http://www.rbroom.com/
Re: $r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn't work
If you have an access handler return OK, then the access handling stops.
Because that handler handled it.
So as far as I know:
$r-push_handlers('PerlAuthenHandler', 'Some::handler');
return DECLINED;
should work...
-- Ryan
- Original Message -
From: Rodney Broom [EMAIL PROTECTED]
To: mod_perl list [EMAIL PROTECTED]
Sent: Saturday, August 31, 2002 6:59 PM
Subject: $r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn't
work
Hi all,
I'm sure I'm just missing something, but I'm stumped.
I've got an access handler that does some tests and then conditionaly does
this:
$r-push_handlers('PerlAuthenHandler', 'Some::handler');
return OK;
Some::handler() starts by printing the current callback to the error log,
which never happens if it's set to run in the 'PerlAuthenHandler'. If I
change the push_handlers() to use 'PerlFixupHandler', then Some::handler()
gets called and I see it in the error log.
What am I doing wrong? I know it has to be me.
---
Rodney Broom
President, R.Broom Consulting
http://www.rbroom.com/
Re: $r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn't work
From: Ryan Parr [EMAIL PROTECTED]
If you have an access handler return OK, then the access handling stops.
Because that handler handled it.
So as far as I know:
$r-push_handlers('PerlAuthenHandler', 'Some::handler');
return DECLINED;
should work...
Yeah, I tried that. I've also tried AUTH_REQUIRED, FORBIDDEN, and DONE. Since the
authentication phase is after the access phase, my guess has been that the return from
the access phase shouldn't effect the authentication phase. That is, of course, unless
the access phase returns something like SERVER_ERROR. Right?
---
Rodney Broom
President, R.Broom Consulting
http://www.rbroom.com/
Re: $r-push_handlers('PerlAuthenHandler', 'Some::handler') doesn'twork
Rodney Broom wrote:
From: Ryan Parr [EMAIL PROTECTED]
If you have an access handler return OK, then the access handling stops.
Because that handler handled it.
So as far as I know:
$r-push_handlers('PerlAuthenHandler', 'Some::handler');
return DECLINED;
should work...
Yeah, I tried that. I've also tried AUTH_REQUIRED, FORBIDDEN, and DONE. Since the
authentication phase is after the access phase, my guess has been that the return
from the access phase shouldn't effect the authentication phase. That is, of course,
unless the access phase returns something like SERVER_ERROR. Right?
What happens if you do:
$r-set_handlers('PerlAuthenHandler', 'Some::handler');
could be that with push_handlers() you have some other handler that
takes over, before Some::handler has a chance to run.
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: Apache::PerlRun weird behavior?
valerian wrote:
Hi I'm new at mod_perl, and I decided to start running my scripts with
Apache::PerlRun so I don't have to rewrite them right away (they're too
'dirty' to run under Apache::Registry). Anyway, I figured it was going
to be easy since PerlRun provides an environment similar to CGI, but
something strange is happening. There's a section in the User Guide that
talks about possible problems one can encounter with referenced
variables, so I figured I'd write a very simple test script to see if
that was the case with my code.
So the weird thing is that it runs fine the first time, but when I
reload the page, it doesn't show the variable I imported from
My::Config, and this is what the output looks like this:
html_dir =
count = 1
And this message shows up in the error.log:
[Sat Aug 31 19:59:15 2002] test.pl: Use of uninitialized value at
/home/val/www/cgi-bin/test.pl line 12.
This is such a simple script, but I can't figure out what I'm doing
wrong. What's even more weird is that if I change my httpd.conf to use
Apache::Registry instead of Apache::PerlRun, the script works fine!
(well the value of $count keeps incrementing, but I expected that).
Could someone please tell me what I'm doing wrong? My settings/code are
shown below:
Copy-n-pasted your conf and the code and I cannot reproduce the problem
with Apache::PerlRun.
Do you have this problem when you run the server under 'httpd -X'?
What mod_perl version are you using? Try to use the latest one. (though
PerlRun didn't change for years).
I've tested with: mod_perl 1.27 (perl 5.6.1 and 5.8.0)
- httpd.conf -
PerlWarn On
PerlTaintCheck On
PerlModule CGI
Alias /cgi-perl/ /home/val/www/cgi-bin/
Location /cgi-perl
SetHandler perl-script
PerlHandler Apache::PerlRun
Options +ExecCGI
allow from all
/Location
- test.pl -
#!/usr/bin/perl -w
use strict;
use CGI;
use My::Config;
use vars qw($count);
my $q = new CGI;
$count++;
print $q-header(-type='text/html');
print html_dir = $CF{'html_dir'}br;
print count = $countbr;
- My/Config.pm -
package My::Config;
use strict;
use Exporter;
use vars qw(@ISA @EXPORT %CF);
@ISA = ('Exporter');
@EXPORT = qw(%CF);
$CF{'html_dir'} = '/home/val/www/htdocs';
1;
--
__
Stas BekmanJAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide --- http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
