On Monday 29 April 2002 22:35, you wrote: > On Monday 29 April 2002 10:57 pm, Marcus Zoller wrote: > > Am Mon, 2002-04-29 um 23.12 schrieb countersync: > > > On Monday 29 April 2002 21:07, you wrote: > > > > Am Mon, 2002-04-29 um 22.55 schrieb Chris Hoeschen: > > > > > I was wondering it there was a way to route HTTP request for > > > > > abc.com to one box and xyz.com to a different box if both > > > > > abc.com and xyz.com > > > > > >... > > > Doesn't sound like a good choice since the addresses are external, > > > the packets are probably comming from the net, and have already been > > > addressed with the single target. The other reply with the HTTP > > > redirect (reccomend apache mod_rewrite, or 2.0 equiv) seems a better > > > choice. > > > > How does the HTTP redirect to another box work if both domains are > > pointing to the same address? > > Suppose abc.com and xyz.com both point to a web server on 11.22.33.44 > > You actually want requests for abc.com to be handled by some machine on > 22.33.44.55, and requests for xyz.com to handled by one on 33.44.55.66 > (why you don't just change the DNS entries beats me, but let's pursue > this idea for now.....) > > The webserver on 11.22.33.44 gets a request for abc.com and responds > with a redirect to 22.33.44.55 (where the server will presumably pretend > to be abc.com), alternatively if the webserver on 11.22.33.44 gets a > request for xyz.com it responds with a redirect to 33.44.55.66 > > Note that these redirects are HTTP redirects - nothing to do with IP > routing, DNS responses etc... All it means is that a browser asking > for abc.com goes to 11.22.33.44, gets redirected to 22.33.44.55, gets a > satisfactory response from there, and the viewer is happy :-) > > Is this helpful ? > > Antony.
The other ways thought of so far, are to use the proxy stuff that comes with apache, write a script to proxy data, use Virtual hosting if they're on the same box, or use external user level applications (like squid etc) to proxy to another address. I should note that no one here is even thinking of suggesting a routing level issue for this, mostly because the routing is already working as can be expected in the best case scenerio.
