Re: Protecting perl-status by IP on a backend server

2005-02-27 Thread Carl Johnstone
> > SetHandler server-status > Order deny,allow > Deny from all > Allow from env=admin_ip > > > I still get > > [client 127.0.0.1] client denied by server configuration Put the access rules in the front-end (non-mod_perl) apache rather than the back-end. Carl

Re: Protecting perl-status by IP on a backend server

2005-02-27 Thread Barry Hoggard
On Feb 27, 2005, at 4:01 PM, Barry Hoggard wrote: My setup: mod_perl/1.999.21 httpd-2.0.53 mod_rpaf-0.5 I have a front-end apache that listens on the server IP, and proxies requests to a mod_perl server listening on several ports of 127.0.0.1. I would like to be able to see the status pages witho

Protecting perl-status by IP on a backend server

2005-02-27 Thread Barry Hoggard
My setup: mod_perl/1.999.21 httpd-2.0.53 mod_rpaf-0.5 I have a front-end apache that listens on the server IP, and proxies requests to a mod_perl server listening on several ports of 127.0.0.1. I would like to be able to see the status pages without having to be logged into the server. Is there