Hi,
I've just started using ModPerl::PerlRunPrefork and mod_perl.
I've been using plain old CGI for a while in a basic MVC framework
but got the following trouble when moving to mod_perl:
- I was manipulating @INC in a BEGIN block but wasn't working.
The main app index.pl is very basic:
use
On Tue, Feb 10, 2009 at 10:44 PM, Patrick Galbraith wrote:
> After looking at it in gdb, I noticed it has something to do with
> Apache2::RequestRec, the header in particular.
My guess is that you're keeping an old CGI or $r object around between
requests, or that this is some kind of special sce
As someone pointed out, these things can be very practical too.
#---
#!/usr/bin/perl
# my nifty cgi-bin
use strict;
use warnings;
our $big_table;
{
package XX;
no strict;
$var1 = 0;
}
sub sub1 {
my $key = shift;
unless (defined($big_table)) {
go_fill_it($big_table);
$XX::va
>> (A solution would be to force all "my" varialbes at the file scope to
>> be "our" and then put the cgi in an anonymous package:)
>
> A file/package-scoped "my" var is not the same thing as an "our" var. One
> example is that a "my" var can't be seen outside of the package/scope it's
> in. A pack
> Variable "$x" will not stay shared at /usr/local/prefork/perl/thing.cgi line
> 10.
Yes, I foolishly looked in the per-virtual-host error log, instead of
the global error log
where the warning was placed neatly.
> which, with a quick googling of 'mod_perl variable will not stay shared',
I was b
Erik Aronesty wrote:
Maybe ModPerl::Registry should do this, but not mod_perl itself. If someone
Yes, it's a problem with ModPerl::Registry, I agree. It's not mentioned here:
http://perl.apache.org/docs/2.0/api/ModPerl/Registry.html#Caveats
Where it should be.
Absolutely, i'll patch the do
Hi,
i've looked into cpan and found a very old Apache::DAV Plugin.
I wonder if mod_perl (2.x) does include access to the DAV Api already or does
not provide anything?
I am looking into a way using DAV with a customized mod_perl module, to extend
the DAV implementation with quota a quota check.
> Maybe ModPerl::Registry should do this, but not mod_perl itself. If someone
Yes, it's a problem with ModPerl::Registry, I agree. It's not mentioned here:
http://perl.apache.org/docs/2.0/api/ModPerl/Registry.html#Caveats
Where it should be.
> is trying to get an old CGI script to work under m
Michael Peters wrote:
Erik Aronesty wrote:
This can not be called "verbose", because it's rather hard to find, but
it's worth reading.
http://perl.apache.org/docs/general/perl_reference/perl_reference.html#toc_Remedies_for_Inner_Subroutines
But normally perl/mod_perl will warn you in the log
Erik Aronesty wrote:
(A solution would be to force all "my" varialbes at the file scope to
be "our" and then put the cgi in an anonymous package:)
A file/package-scoped "my" var is not the same thing as an "our" var. One example is that a "my" var
can't be seen outside of the package/scope it'
Erik Aronesty wrote:
mod_perl should be *extremely* verbose in pointing this change out to
developers, as
it is *extremely* difficult to diagnose.
Maybe ModPerl::Registry should do this, but not mod_perl itself. If someone is trying to get an old
CGI script to work under mod_perl then they'd
Erik Aronesty wrote:
(A solution would be to force all "my" varialbes at the file scope to
be "our" and then put the cgi in an anonymous package:)
On Thu, Feb 12, 2009 at 10:33 AM, Erik Aronesty wrote:
-8<-- Start Bug Report 8<--
1. Problem Description:
(A solution would be to force all "my" varialbes at the file scope to
be "our" and then put the cgi in an anonymous package:)
On Thu, Feb 12, 2009 at 10:33 AM, Erik Aronesty wrote:
> -8<-- Start Bug Report 8<--
> 1. Problem Description:
>
> It's well known
-8<-- Start Bug Report 8<--
1. Problem Description:
It's well known that file-scoped lexicals don't work intuitively in
CGI programs under mod_perl.
When mod_perl calls the same CGI program twice, file-scoped lexicals
are not rebound.
Some people are aware
In a message dated 2009-2-12 22:39:48, eric.b...@barclayscapital.com writes:
> Nope, selinux is disabled on /etc/selinux/config
Or you may take a look at this article:
_http://blog.modsecurity.org/2009/01/building-qa-test-cases-from-waf-data.html
_
(http://blog.modsecurity.org/2009/01/buil
Carl,
I may have missed it, but did you say at what point you were seeing the
segfault? I assume you mean at startup, but can you confirm?
E
> -Original Message-
> From: Carl Brewer [mailto:c...@bl.echidna.id.au]
> Sent: Wednesday, January 28, 2009 7:43 AM
> To: Philippe M. Chiasson
>
16 matches
Mail list logo
