Re: Multiple web site redirection
On Wednesday 08 December 2010 21:03:59 Craig Reynolds wrote:
> Hi all,
> I apologise if this is not the right place to ask this;
> I have two web servers, both serving a multitude of different sites and
> domains, both HTTP and HTTPS. Lets call them 220.127.116.11 and 18.104.22.168.
> We're leaving the hosting provider where they live, and they being
> migrated to two identical servers at another, lets say 22.214.171.124 and 126.96.36.199.
> Each server has around 8 additional IPs where the SSL sites are bound.
> As we don't control the DNS for the majority of these, it seems unlikely
> that I can get dozens of clients to change TTL and A records at the same
> time. I don't want them both to be live in parallel, and I don't want
> to migrate site by site and take the next millennium to complete the
> What are thoughts about the best way to accomplish this?
Just use Apache's reverse proxy for a while and let your customers know that
they'll need to change their DNS to the new address by [whatever date you
deem OK]. Don't delay this for too long: it will mean doubling your network
bandwith (since HTTP packets will travel from 188.8.131.52 to 184.108.40.206 and back)
and you'll increment latency proportionally to that.
Having a look at your logs will tell when all DNS are reconfigured and
An example for a domain:
ProxyPass / http://220.127.116.11/
ProxyPassReverse / http://18.104.22.168/
Allow from all
The SSL sites throw no problem except if they are using client-side
certificates for validation. The "usual" case (no client certs) would go
more or less like this:
SetEnvIf User-Agent ".*MSIE.*" nokeepalive ssl-unclean-shutdown
ProxyPass / https://22.214.171.124/
ProxyPassReverse / https://126.96.36.199/
Allow from all