I am trying to figure this out and I always seem to have trouble configuring apache to do more than basic stuff... I have a web server that has several cnames assigned to it. I want srv1.tobyhouse.com to be served by apache. I want to proxy connections to www.tobyhouse.com to cms.tobyhouse.com (different system) If I do this... <VirtualHost www.tobyhouse.com:*> ProxyPass / http://cms.tobyhouse.com ProxyPassReverse / http://cms.tobyhouse.com </VirtualHost> then I am good but it seemed to not pull the assets like css and javascripts from cms.tobyhouse.com When I did this... <VirtualHost www.tobyhouse.com:*> RedirectPermanent / http://cms.tobyhouse.com </VirtualHost> It sent ALL traffic over to the other server which is clearly not what I want. How can handle this? Must I give a unique ip address to www.tobyhouse.com? Craig
Craig White wrote:> I am trying to figure this out and I always seem to have trouble > configuring apache to do more than basic stuff... > > I have a web server that has several cnames assigned to it. > > I want srv1.tobyhouse.com to be served by apache. > I want to proxy connections to www.tobyhouse.com to cms.tobyhouse.com > (different system) > > If I do this... > > <VirtualHost www.tobyhouse.com:*> > ProxyPass / http://cms.tobyhouse.com > ProxyPassReverse / http://cms.tobyhouse.com > </VirtualHost> > > then I am good but it seemed to not pull the assets like css and > javascripts from cms.tobyhouse.comThat should work - but I'd put a trailing / on the target. The files that don't appear to work are probably cached in your browser or an intermediate cache. Check the logs to see if a request even came in. You can get finer-grained control by using rewriterules with the P flag but you shouldn't need it. Just make sure the links from the backend server are all relative and don't mention its real hostname. -- Les Mikesell lesmikesell at gmail.com
Craig White wrote on Mon, 05 May 2008 14:57:05 -0700:> <VirtualHost www.tobyhouse.com:*>this is very old-fashioned and unreliable syntax, use this instead: http://httpd.apache.org/docs/2.2/vhosts/name-based.html> RedirectPermanent / http://cms.tobyhouse.com> It sent ALL traffic over to the other server which is clearly not what I > want.I don't understand. Isn't that exactly what you want, redirect all traffic for www.tobyhouse.com to cms.tobyhouse.com?> How can handle this? Must I give a unique ip address to > www.tobyhouse.com?Ah, you have several virtual hosts on it and all of them get redirected to cms.tobyhouse.com? That's the result of the wrong virtual host syntax you use. Use name-based virtual hosts and it will work. Why don't you solve this at dns level? Wouldn't that be much "cleaner"? Kai -- Kai Sch?tzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com