> My first suggestion is comment out the proxy stuff for now, and just > see if you can get vhosts working in general. You can test this by > giving the vhosts a different DocumentRoot from the main server, and > you'll know it's working based on what DocumentRoot is being served. VHost is running, because if i try to acces http://mantis.colonizaciontest.com.uy/ i get access .. so DNS config an VHosts are Ok I got it to work now wit the VirtualHost block that chris provided But my question is about unnecessary overhead now. 192.168.100.5 will serve as proxy for 192.168.100.6 all the time .. this means unnecessary processing and network overhead. The main problem is that our router/firewall sends all requests on port 80 to one server only (192.168.100.5), despite a subdomain specified in the URL. So that is why we thought about using 192.168.100.5 as proxy for 192.168.100.6 Is there a way to accomplish this same goal, but by passing the request to 192.168.100.6 withjou having 192.168.100.5 involved on the rest of the communication?? THANKS TONS! PD Using apache 2.2.3 --------------------------------------------------------------------- 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: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|