On Mon, 2008-05-05 at 17:27 -0500, Les Mikesell wrote: > Stephen Harris wrote: > > On Mon, May 05, 2008 at 03:14:35PM -0700, Craig White wrote: > >> On Mon, 2008-05-05 at 17:08 -0500, Les Mikesell wrote: > >>> Craig White wrote: > >>>> <VirtualHost www.tobyhouse.com:*> > >>>> ProxyPass / http://cms.tobyhouse.com > >>>> ProxyPassReverse / http://cms.tobyhouse.com > >>>> </VirtualHost> > >>> That should work - but I'd put a trailing / on the target. The files > > > >> OK - well adding the backslash to the end seemed to fix the issue with > >> css but the problem is that stuff that is going to srv1.tobyhouse.com is > >> also proxied over to the same site and I want that to stay at home. > > > > Try putting a "ServerName www.tobyhouse.com" entry into the VirtualHost > > config. > > I missed that - the name in the VirtualHost directive will just be > evaluated as an IP address. To actually identify a named virtual host > the ServerName must match what the client sends the the Host: header. > ServerName can only have one entry. If there are more names this host > should accept you can have a ServerAlias entry with multiple names. If > none of your virtualhost entries have a match and you don't have an > explict default, the first one is used. ---- yeah...I ended up... NameVirtualHost *:80 <VirtualHost *:80> ServerName www.tobyhouse.com ProxyTimeout 10000 ProxyPass / http://cms.tobyhouse.com/ ProxyPassReverse / http://cms.tobyhouse.com/ </VirtualHost> <VirtualHost *:80> ServerName srv1.tobyhouse.com DocumentRoot /var/www/html </VirtualHost> awesome...thanks Les/Stephen - I can now take my time and figure out what we're going to do before I make any DNS changes Craig