We are transitioning from static pages (on one server) to a CMS
(running on another server - unfortunately IIS). To make the
transistion as transparent as possible, we have set up a Linux/Apache
2.0 reverse proxy which has become the WWW machine. It directs URLs to
either the old server or the new server, depending upon whether the
department or office has converted their content into the CMS yet, or
not.

This is working well, but here is the challenging part. We had some
VirtualHosts on the old server. For example: its.domain.com used to
equal www.domain.com/offices/its/ (you could get to the pages with
either URL. If you came via its.domain.com then the user saw that
domain as long as they were clicking relatively addressed links.

We'd like to do the same thing when those page move to the CMS machine,
but there is a problem. The CMS writes some things (like scripts and
images) using links relative to the IIS web root. For example:
<img src="/uploadedImages/offices/its/image.gif">

So how does one set up the VirtualHost (and/or the Proxy config) on the
WWW proxy machine so that some directories (like uploadedImages) are
proxied to the CMS machine, but NOT affected by the VirtualHost root
definition?

Is this even possible?

Currently we are simply using a REDIRECT directive in the VirtualHost
definition, but that means that the user loses the virtual domain as
soon as they are redirected.

You may also need to know that the virtualhost info is defined in a
vhost.conf while the reverse proxy stuff is defined in a separate
revproxy.conf.

Any suggestions would be greatly appreciated!

CheekyGeek wrote:

> [chop]
> Any suggestions would be greatly appreciated!
>

http://www.apacheweek.com/features/reverseproxies

--
Nick Kew