upgrade to cvs version of apache on the proxy. cvs version solveds this problem.
best regards,
On Mon, May 13, 2002 at 06:57:07PM +1000, Ian Macdonald wrote:
> Hi All.
>
> I'm setting up a new server and wish to run two Apache configurations,
> one vanilla and one mod_perl. I've configured pret
sounds like the XSLoader vs. DynaLoader issue which only exists in 5.6.x.
try updating modperl-2.0-cvs, there is a better workaround in there for
the issue now.
On Fri, 24 May 2002, Jie Gao wrote:
> "Segmentation fault" happens when accessing /export/softwares/data, a
> subdirectory which does not have an .htaccess file itself, but a
> subdirectory of which has an .htaccess file containing:
hmm. you might want to try building modperl with MP_DEBUG=1 a
modperl assumes libperl is installed where perl puts it by default, but it
seems some distributions (or maybe even perl hints) do something else.
the Makefile only uses it to relink mod_perl.so if libperl has changed,
which is only useful when perl is build rebuilt often. so now if
the libperl
Hi,
sorry if this has already been discussed, just point me to archives then.
I'm building a last night CVS checkout of mod_perl 2 against a last
night CVS checkout of apache 2 and Per 5.6.1. Here's what happens:
morris@melchior:/usr/src/modperl-2.0> perl Makefile.PL
MP_APXS=/home/httpd2/bin/a
On Wed, 22 May 2002, Doug MacEachern wrote:
> On Thu, 23 May 2002, Jie Gao wrote:
>
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to Thread 1024 (LWP 15349)]
> > 0x4031575d in modperl_mgv_lookup (symbol=0x0) at modperl_mgv.c:134
> > 134 if (!symbol->hash) {
> > (
How does the Carp module interact with mod_perl? Is there a built-in catch
for croak or does it actually kill the child process, for instance?
Thanks,
Christian
-
Christian Gilmore
Technology Leader
GeT WW Global Applications Development
IBM Software Group
Andrew Ho wrote:
> Hello,
>
> GY>well, it's an API in that it doesn't do anything for you except provide
> GY>an API. meaning, I'd expect Apache::AuthDigest to work as so:
> GY>
> GY>PerlAuthenHandler Apache::AuthDigest
> GY>
> GY>all this module does is provide methods that parallel
> GY>$r->
hi
sorry, my english dont is good ;)
i have one big problem,
i using apache2, modperl2 and perl 5.6.1
Apache/2.0.37-dev (Unix) mod_perl/1.99_02-dev Perl/v5.6.1
when i add this line in httpd.conf
PerlModule DBI
or
Perlrequire startup.conf
startup.conf:
use DBI;
1;
if i use it, httpd don't
Hello,
GY>well, it's an API in that it doesn't do anything for you except provide
GY>an API. meaning, I'd expect Apache::AuthDigest to work as so:
GY>
GY>PerlAuthenHandler Apache::AuthDigest
GY>
GY>all this module does is provide methods that parallel
GY>$r->get_basic_auth_pw() and $r->note_basic
Andrew Ho wrote:
> Hello,
>
> GY>Apache::DigestAPI is a release of Recipe 13.8 in the Cookbook - a simple
> GY>API for supporting Digest authentication a la mod_digest.c from the
> GY>Apache distribution.
>
> I think this is a great idea. I'm a huge fan of digest authentication as a
> simple
Hello,
GY>Apache::DigestAPI is a release of Recipe 13.8 in the Cookbook - a simple
GY>API for supporting Digest authentication a la mod_digest.c from the
GY>Apache distribution.
I think this is a great idea. I'm a huge fan of digest authentication as a
simple basic authentication replacement, an
hi all...
I wanted to present Apache::DigestAPI as an RFC. the module can be downloaded here
for
trials:
http://www.modperlcookbook.org/~geoff/modules/Apache-DigestAPI-0.01.tar.gz
basically, Apache::DigestAPI is a release of Recipe 13.8 in the Cookbook - a simple
API
for supporting D
On Thu, May 23, 2002 at 11:21:31AM -0400, Fran Fabrizio wrote:
> >
> >
> >(I haven't re-tested Apache::AuthCookieDBI.)
> >
> >I have no idea why POST _doesn't_ work, mind you...
> >
>
> For what it's worth, my setup with AuthCookieDBI works just fine with POST.
I agree that is _should_; I've wri
At 16:41 23.05.2002, David Jacobs wrote:
>I've had trouble benchmarking some of my mod_perl scripts on my desktop.
>The http_load tool we usually use (all under RedHat) works fine with
>static pages or CGI, but when I use it on mod_perl scripts I get a "byte
>count wrong" error. This could be b
>
>
>(I haven't re-tested Apache::AuthCookieDBI.)
>
>I have no idea why POST _doesn't_ work, mind you...
>
For what it's worth, my setup with AuthCookieDBI works just fine with POST.
-Fran
Matt Sergeant wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> This is just a heads up on something I've not seen documented in either the
> Eagle book or in the Cookbook (at least not that I can find).
>
> If you create a subrequest via $r->lookup_file(), the per_dir_config entr
17 matches
Mail list logo