t; number (starting at 0). The documentation seems a little misleading
> (http://perl.apache.org/docs/2.0/api/Apache2/Connection.html#C_id_). Anyone
> else ever use this method for this purpose?
> Thanks,
> Paul
>
> On Wed, Oct 14, 2009 at 3:14 PM, Adam Woodworth wrote:
>>
>
Say you're using the prefork MPM and you have 200 Apache children. Is
there a way, within mod_perl, to find out what the server number is
for the apache child in which mod_perl is running? Not the PID
number, but the server number (or whatever it's called) -- i.e., a
number between 1 and 200 that
If I do this with mod_perl 2.0.3 from inside my mod_perl application:
print STDERR "timeout = " . $r->server->timeout() . "\n";
I get this:
[Thu Sep 18 16:28:01 2008] [error] [client 192.168.1.40] Can't locate
object method "timeout" via package "Apache2::ServerRec" at
/var/httpd/lib/perl/SiteSp
I'm using mod_perl 2.0.3 with Apache 2.2.9 and mod_proxy for reverse
proxying. Is there a way, from my mod_perl application, that I can
tell when the connection to the backend server in mod_proxy timed out?
I.e., mod_proxy made a connection to the backend, but the backend
didn't respond in the co
Thank you for the clarification, Geoff!
I've traced this missing cookie header issue down to a very strange
problem: it seems to be a timing issue somehow. If I put a usleep(1)
in our code at the start of our perl Response filter, the cookies are
no longer missing for each response. For that ma
Yup, I'm directly hitting the application, there's nothing in between
my client and the server.
On Dec 19, 2007 1:39 PM, Torsten Foertsch <[EMAIL PROTECTED]> wrote:
> On Wed 19 Dec 2007, Adam Woodworth wrote:
> > Content-Length: 123434 <-- **missing from above**
>
Hi,
I'm using a web stack consisting of Apache 2.2.6, mod_perl 2.0.3, and
libapreq 2.10 (from their svn branch), and I'm seeing a problem where
some headers are sometimes missing from the HTTP response.
Specifically, we are setting a couple cookies from our mod_perl
application, and about half th
Hi Everyone,
My current LAMP stack is using Apache 2.0.54 and mod_perl 2.0.0-RC4,
and I'm doing something very much like what is mentioned in a previous
mod_perl mailing list post from 2 years ago, the thread of which can
be seen here:
http://www.gossamer-threads.com/lists/modperl/modperl/79672?s
