On Tuesday 15 May 2007 22:33, Walt Reed wrote:
> I would prefer however to put all my test modules for this migration in the
> /usr/local/apache2/perllib space, but looking at the mod_perl configure
> options, I didn't see which option specified this... MP_AP_PREFIX?
> MP_AP_DESTDIR? Neither one of
Modify @INC to only load the libraries you need, and make sure to
install the MP1 modules in a different location than the MP2 ones.
Basically, install the 'default' server perl modules normally, and
install the 'other' ones in a special directory that you then modify
@INC to include through u
On Tue, May 15, 2007 at 04:05:38PM -0400, Michael Peters said:
> Walt Reed wrote:
> > The apache part isn't the problem. I can easily run on different ports,
> > and whatnot. In fact, both apache's are working fine independantly, so
> > it's just the perl / mod_perl issue. When I do a "make install
On May 15, 2007, at 4:05 PM, Michael Peters wrote:
Walt Reed wrote:
The apache part isn't the problem. I can easily run on different
ports,
and whatnot. In fact, both apache's are working fine
independantly, so
it's just the perl / mod_perl issue. When I do a "make install" of
mod_perl 2.x
On May 15, 2007, at 3:49 PM, Perrin Harkins wrote:
My approach would be to install two copies of perl, and put one of
them on each. Or, install each in a local perl lib directory rather
than the system dir. (Local installs of CPAN modules are well-covered
elsewhere.)
I'd second the latter s
Walt Reed wrote:
> The apache part isn't the problem. I can easily run on different ports,
> and whatnot. In fact, both apache's are working fine independantly, so
> it's just the perl / mod_perl issue. When I do a "make install" of
> mod_perl 2.x I don't want mod_perl 2 based perl modules tromping
The apache part isn't the problem. I can easily run on different ports,
and whatnot. In fact, both apache's are working fine independantly, so
it's just the perl / mod_perl issue. When I do a "make install" of
mod_perl 2.x I don't want mod_perl 2 based perl modules tromping all
over the existing mo
Walt Reed wrote:
I have a need to install both apache 1.3.x / mod_perl 1.x and apache
2.2.x / mod_perl 2.x on the same machine.
Googling returns some hits from 2004 that mention MP_INST_APACHE2=1, but
that option no longer exists in current versions of mod_perl 2.
Didn't see anything obvious
On 5/15/07, Walt Reed <[EMAIL PROTECTED]> wrote:
I have a need to install both apache 1.3.x / mod_perl 1.x and apache
2.2.x / mod_perl 2.x on the same machine.
[...]
Suggestions?
My approach would be to install two copies of perl, and put one of
them on each. Or, install each in a local perl
hi
ouch.
the only suggestion i have is to reasess your needs. really- you'll
spend at least 10 hours dicking around with the network config to say
nothing about httpd.conf. if you get paid over $10. and hour, that makes
it worth it buy a new machine.
-Original Message-
From: Walt Reed [
I have a need to install both apache 1.3.x / mod_perl 1.x and apache
2.2.x / mod_perl 2.x on the same machine.
Googling returns some hits from 2004 that mention MP_INST_APACHE2=1, but
that option no longer exists in current versions of mod_perl 2.
Didn't see anything obvious in the install manu
use Apache::RequestRec;
?
What version of mod_perl are you running? The above line makes me thing
you're running an reall old version of mod_perl2 from prior to the
namespace change, which is probably a really bad idea, and may explain
why Auth isn't working right.
Adam
-Original Message---
Michael Peters wrote:
> Moritz Maisel wrote:
>
>>Hi List,
>>
>>I wrote a PerlAuthenHandler to authenticate users that access a
>>webservice. I supposed that by returning either "OK" or
>>"HTTP_UNAUTHORIZED" back to apache2 it will allow or deny acces due to
>>the "require valid-user" directive tha
2007/5/15, Michael Peters <[EMAIL PROTECTED]>:
The HTTP codes are HTTP return codes, not handler return codes. Use
FORBIDDEN
instead.
I already tried (and now tried again) to use "return FORBIDDEN" instead of
"return HTTP_UNAUTHORIZED" without success.
:-(
Moritz Maisel wrote:
> Hi List,
>
> I wrote a PerlAuthenHandler to authenticate users that access a
> webservice. I supposed that by returning either "OK" or
> "HTTP_UNAUTHORIZED" back to apache2 it will allow or deny acces due to
> the "require valid-user" directive that I set.
> My problem is, t
Hi List,
I wrote a PerlAuthenHandler to authenticate users that access a webservice.
I supposed that by returning either "OK" or "HTTP_UNAUTHORIZED" back to
apache2 it will allow or deny acces due to the "require valid-user"
directive that I set.
My problem is, that apache executes my handler, bu
Hello All,
> -Original Message-
> From: Shah, Sagar: IT (LDN)
> Sent: 17 April 2007 09:39
> To: 'Charlie Katz'; modperl@perl.apache.org
> Cc: Perrin Harkins; [EMAIL PROTECTED]; [EMAIL PROTECTED];
> Client Research Development
> Subject: RE: "Insecure dependency in eval while running set
17 matches
Mail list logo
