[EMAIL PROTECTED] wrote:
>
> I've searched a lot throug the archive of this mailinglist and found lot's
> of postings also pointing to Segmentation fault (11), but usually the
> suggested solution was to have a look in the SUPPORT-file in the mod_perl
> directory.
Actually, the suggested solution
I have a problem with getting mod_perl 2.0.3 to work on our AIX5.3 with
IBM-Webserver (based on Apache 2.0.47) and perl 5.8.2
When I insert the line
"LoadModule perl_module modules/mod_perl.so"
to the httpd.conf and I then restart the webserver, then the following
entries appear in the error
Why does the Authentication handler been called many times unnecessarily for
a url pattern like (http://localhost/test), Is there any way to ignore
within the handler it self.
Is it advisable to use $r->is_initial_req; and return OK.
.
--
View this message in context:
http://w
On 1/24/07, Octavian Rasnita <[EMAIL PROTECTED]> wrote:
Does anyone have an example of setting Apache2 that use a reverse proxy with
mod_proxy?
There's no trick to it. The examples in the mod_proxy documentation
should work. You will need to turn ProxyPreserveHost on if you want
to use NameVi
what I meant was different thing, normally auth handlers got REDIRECT or may
be HTTP_MOVED_TEMPORARILY.
where necessary.
in httpd we might have a uri() or anyother thing
will say query string as /test which is quite right but
I just want to know is there any way to get where client intended to
On Jan 24, 2007, at 3:56 PM, Octavian Rasnita wrote:
Hi all,
Does anyone have an example of setting Apache2 that use a reverse
proxy with mod_proxy?
I have set my own, but I receive some errors in the error log and I
don't know how to solve them, and I also don't know how to make the
I
Hi all,
Does anyone have an example of setting Apache2 that use a reverse proxy with
mod_proxy?
I have set my own, but I receive some errors in the error log and I don't
know how to solve them, and I also don't know how to make the IP of the
visitor appear in the back-end server's access log
On Jan 24, 2007, at 2:35 PM, Jonathan Mangin wrote:
Thanks Geoff,
the gist is what I needed for now. So I'm guessing (again)
that the xsubs are living in libapreq.so*. Is that right?
Is it in import() (in APR::Request) where the loading
occurs?
These are my last questions on the subject. Lo
> >
> > Glancing at docs for ExtUtils::XSBuilder leads me to believe
> > there should be a Perl function named args_status (probably)
> > in APR::Request, but no.
>
> no, it wouldn't be if the function is defined in XS.
>
> > Can someone point me to a user list
> > for libapreq2?
>
> you can
On 1/24/07, Robert Landrum <[EMAIL PROTECTED]> wrote:
Perrin Harkins wrote:
> My guess is that $self has a lifespan longer than one request, so you
> are trying to use a $r object from a previous request.
Would $r still be defined in that instance?
Yes. What you're checking is that the refere
Perrin Harkins wrote:
My guess is that $self has a lifespan longer than one request, so you
are trying to use a $r object from a previous request.
Would $r still be defined in that instance?
Rob
On 1/24/07, Joel Gwynn <[EMAIL PROTECTED]> wrote:
My understanding is that PerlSetVar is not a per-request directive.
What am I missing?
You mean dir_config? It's not per-request, but I'm guessing that $r
in your code is an Apache2::RequestRec object, which is per-request.
You have to call dir
On 1/24/07, Perrin Harkins <[EMAIL PROTECTED]> wrote:
On 1/24/07, Joel Gwynn <[EMAIL PROTECTED]> wrote:
> OK. I replaced that line with a hard-coded file path, and now it's
> looking much better. So I guess it's something about the Request
> object.
My guess is that $self has a lifespan longer
On 1/24/07, Joel Gwynn <[EMAIL PROTECTED]> wrote:
OK. I replaced that line with a hard-coded file path, and now it's
looking much better. So I guess it's something about the Request
object.
My guess is that $self has a lifespan longer than one request, so you
are trying to use a $r object fro
Raf wrote:
> On Wed, 24 Jan 2007, Perrin Harkins wrote:
>
>>On 1/24/07, Raf <[EMAIL PROTECTED]> wrote:
>>
>>>The code base I'm profiling is very big, monolithic and convoluted. I
>>>felt that level of granularity given by smallprof would probably give me
>>>more coverage - which I believe I need.
On Wed, 24 Jan 2007, Perrin Harkins wrote:
> On 1/24/07, Raf <[EMAIL PROTECTED]> wrote:
> > The code base I'm profiling is very big, monolithic and convoluted. I
> > felt that level of granularity given by smallprof would probably give me
> > more coverage - which I believe I need.
>
> Usually tha
On 1/24/07, Joel Gwynn <[EMAIL PROTECTED]> wrote:
On 1/24/07, Robert Landrum <[EMAIL PROTECTED]> wrote:
> Joel Gwynn wrote:
> > Interesting. I just might be doing that:
> > $config_file = $self->param('r')->dir_config('CONFIG_FILE');
> >
> > In my section, I have this:
> >
> > PerlSetVar CONFIG
On 1/24/07, Robert Landrum <[EMAIL PROTECTED]> wrote:
Joel Gwynn wrote:
> Interesting. I just might be doing that:
> $config_file = $self->param('r')->dir_config('CONFIG_FILE');
>
> In my section, I have this:
>
> PerlSetVar CONFIG_FILE /projects/funnyr_dev/private/config.ini
>
> And of course
Joel Gwynn wrote:
Interesting. I just might be doing that:
$config_file = $self->param('r')->dir_config('CONFIG_FILE');
In my section, I have this:
PerlSetVar CONFIG_FILE /projects/funnyr_dev/private/config.ini
And of course I'm not using flock on that file. Hmmm.
Try changing that up...
> Wrong list? That explains some [EMAIL PROTECTED]
> The 1st page of libapreq2 docs says:
>
> o Mailing Lists:
>
> user lists:
>C/C++ API - [EMAIL PROTECTED]
> Perl API - modperl@perl.apache.org
lots of apreq folks hang out here as well, so no worri
Joel Gwynn wrote:
Here's my backtrace, any ideas?
#0 0xb7a58743 in modperl_dir_config (my_perl=0x81b6eb0, r=0x823ce98,
s=0x203a6e6f,
key=0x8800c38 "CONFIG_FILE", sv_val=0x0) at modperl_util.c:516
#1 0xb78dae84 in XS_Apache2__RequestRec_dir_config
(my_perl=0x81b6eb0, cv=0x82cd074)
at Requ
- Original Message -
From: "Jonathan Vanasco" <[EMAIL PROTECTED]>
To: "Geoffrey Young" <[EMAIL PROTECTED]>
Cc: "Jonathan Mangin" <[EMAIL PROTECTED]>;
Sent: Tuesday, January 23, 2007 11:59 AM
Subject: Re: Find source for Apache2::Request::args_status
>
> On Jan 23, 2007, at 11:40 AM, G
Tracy12 wrote:
> In my mod_perl authentication module I have the following to get the url
> without the ticket parameter
>
> my $uri_parsed = $r->parsed_uri;
> my $unparsed = $uri_parsed->unparse();
>
> but if the user hits the url as follows
>
> http://localhost/t
On 1/24/07, Raf <[EMAIL PROTECTED]> wrote:
The code base I'm profiling is very big, monolithic and convoluted. I
felt that level of granularity given by smallprof would probably give me
more coverage - which I believe I need.
Usually that's the reason you use DProf -- it gives you the big
pict
Hi Philip,
On Tue, 23 Jan 2007, Philip M. Gollucci wrote:
> Raf wrote:
> > Apologies for the X-post. It seemed appropriate.
> >
> Mot off the top of my head, why are you using Apache::SmallProf and not
> Apache::Dprof -- the previous is usually too low level.
The code base I'm profiling is very
25 matches
Mail list logo
