The mod_perl 1.31 release candidate "Works with Perl 5.10" is ready. It can be
downloaded here:
http://www.apache.org/~gozer/mp1/mod_perl-1.31-rc1.tar.gz
MD5: 7cda8676120ff6654bcbe923a2ff5747
SHA1: d8d2d4ad36d134a098601083ed4826664bb8a6cf
The summary of what has changed since 1.30 are (from Ch
Try PerlSetEnv instead :)
- Original Message -
From: "Tad Johnston" <[EMAIL PROTECTED]>
To: "Tad Johnston" <[EMAIL PROTECTED]>
Cc: "Adam Prime" <[EMAIL PROTECTED]>;
Sent: Friday, December 21, 2007 9:06 PM
Subject: Re: PerlAccessHandler problems
Correction*
SetEnv PROXY_BIND localho
Correction*
SetEnv PROXY_BIND localhost
Tad Johnston wrote:
The error log only says what it can't find which is the table it's
trying to query from the database (because of course it's querying the
wrong database). The $ENV{PROXY_BIND} variable should be setting it
to the proper database whi
The error log only says what it can't find which is the table it's
trying to query from the database (because of course it's querying the
wrong database). The $ENV{PROXY_BIND} variable should be setting it to
the proper database which it's not.. The problem is when I do a warn
using within th
What does the error_log say?
Adam
Tad Johnston wrote:
I'm having problems trying to use an access handler within mod_perl2.
If I have it in the conf file it returns a 500 Internal Server Error and
if I don't include the PerlAccessHandler line, it runs the page just
fine. What's happening is
I'm having problems trying to use an access handler within mod_perl2.
If I have it in the conf file it returns a 500 Internal Server Error and
if I don't include the PerlAccessHandler line, it runs the page just
fine. What's happening is when it is turned on my $ENV for my proxy
gets set to a
-8<-- Start Bug Report 8<--
1. Problem Description:
MP_CODE_ATTRS() doesn't work under perl 5.10.0.
I discovered this when trying to use a PerlOutputFilterHandler and upgraded
from 5.8.8 to 5.10.0. Under 5.10.0, sometimes the filter would run, sometimes
no
Colin Wetherbee wrote:
> Have any of you used mod_perl with Perl 5.10 yet? Are there any gotchas
> to consider?
Apparently so.
I have found the cause of my sometimes-it-works sometimes-it-doesnt
problem for PerlOutputFilterHandlers.
I tracked the problem down to MP_CODE_ATTRS(), called from mod
Michael Schout wrote:
> [Fri Dec 21 10:57:47 2007] [error] an unknown filter was not added:
> Foo::Filter::StripWhiteSpace
in addition, with PerlTrace enabled, I get:
modperl_filter_add_request: a non-mod_perl OutputFilter handler
Foo::Filter::StripWhiteSpace configured.
Regards,
Michael Schout
Andreas J. Koenig wrote:
>> On Thu, 20 Dec 2007 11:38:02 -0500, Colin Wetherbee <[EMAIL PROTECTED]>
>> said:
>
> > Have any of you used mod_perl with Perl 5.10 yet? Are there any
> > gotchas to consider?
>
> Modperl1 doesn't work, patch available. As for modperl2 I don't know.
I ap
Andreas J. Koenig wrote:
> Modperl1 doesn't work, patch available. As for modperl2 I don't know.
I've been running 5.10 in my modperl2/apache2.2 sandbox development
environment since yesterday. Haven't run into any issues related to
5.10 yet, but its still early on for me :).
Regards,
Michael S
John Siracusa wrote:
> On 12/21/07 2:32 AM, Andreas J. Koenig wrote:
>> I fear I do not understand enough of mod_perl to volunteer to make a
>> release.
>
> Me neither, but have you at least contacted the mod_perl maintainers about
> this? Perhaps you could file a bug on rt.cpan.org even?
the
On 12/21/07 2:32 AM, Andreas J. Koenig wrote:
> I fear I do not understand enough of mod_perl to volunteer to make a
> release.
Me neither, but have you at least contacted the mod_perl maintainers about
this? Perhaps you could file a bug on rt.cpan.org even?
-John
13 matches
Mail list logo
