On Dec 17, 2005, at 5:56 PM, Frank Wiles wrote:
The best way to do this is to use the virtual hosts on the front
end to your advantage. So on the front end you "tell" the backend
which domain it came from:
<VirtualHost domain.com:80>
ProxyPass / http://localhost:8080/domain.com/
ProxyPassReverse / http://localhost:8080/domain.com/
</VirtualHost>
By passing in the domain this way you can see where it came from.
I'm sure there are probably a number of other ways to get this done,
but that was the first that popped into my head.
Unfortunately I don't have access to the httpd.conf file for the front
end server.
It's managed, so I don't have root either. I do have ftp access and an
.htaccess
file.
On the back end server I have access to the httpd.conf file, but not
root access.
I build on a locally on Mac OSX 10.3.9 using Apache2/mod_perl2 then
upload
the static files to the front end and the perl modules to the backend.
Also, any reason you're writing your own IP restrictions instead of
just using allow from/deny from in Apache?
I'm writing them myself because they will be a scalable part of my code
eventually
allowing for IPs dynamically with subscription.
Thanks
Boysenberry
boysenberrys.com | habitatlife.com | selfgnosis.com
