'nite I'll try your tips tomorrow. Thanks a lot.
> If you want to get your hands really dirty, you can also > leave mod_headers aside and set www.example.com statically > in /etc/hosts to point to the backend. That way the proxy > server will still believe that he is www.example.com via > servername, but when you proxy to www.example.com it will > go to the backend via /etc/hosts with the right host-header > to let the backend generate the correct URLs. Not that I > would recommend it, but I have seen this in practice... I thought about another approach : leaving as is my public DNS zone, and modifying my private one to distribute private IP for public domain names. My Reverse Proxies have just to be taught to use the private DNS, and all I have to do is to configure the VH app.public.zone with ProxyPass / app.public.zone, app.public.zone being resolved to the IP app.private.zone had previously. Seems to be the same idea you describe, but with more flexibility & robustness - thanks to real DNS records. Anothet thanks. Regards, Al. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
