How to get the port used by the request

2010-09-01 Thread Cédric Bertolini
Hello, When a request is handled by mod_perl, I'd like to know what port was used to request the server. But $r->server->port always returns 0. I have tested $r->main and $r->prev, but the problem doesn't come from here. And I didn't find any other way to get the port. Even $r->uri and such don't

Re: How to get the port used by the request

2010-09-01 Thread Torsten Förtsch
On Wednesday, September 01, 2010 12:07:43 Cédric Bertolini wrote: > When a request is handled by mod_perl, I'd like to know what port was used > to request the server. But $r->server->port always returns 0. I have tested > $r->main and $r->prev, but the problem doesn't come from here. And I didn't

Re: APR::ArrayHeader

2010-09-01 Thread Torsten Förtsch
On Tuesday, August 31, 2010 22:28:21 Anton Petrusevich wrote: > I was unable to find the answer how to use such an object. > ServerRec::names returns object like this: > > $VAR1 = bless( do{\\(my $o = 19244608)}, 'APR::ArrayHeader' ); > > > I know it maps to apr_array_header_t structure, but i

Strange behaviour with Pseudo-Proxy script

2010-09-01 Thread Winfried Neessen
Hi, I am having a strange issue with a mod_perl handler which I've written lately. A little background. we are using a mod_perl script for our self-developed MS .NET application. The application connects to the frontend server, where the mod_perl "proxy" is running. The script does some k

Re: Strange behaviour with Pseudo-Proxy script

2010-09-01 Thread Fred Moyer
Aside from posting the source code so that we can peruse and say "That might be it", you might try putting a non blocking reverse proxy such as Perlbal (my favorite, and darn tootin' fast), Nginx, or Varnish in front of your mod_perl instance so that it does the dirty work of connection handling an