On Thu, 24 Apr 2008 20:34:10 +0800 (CST)
Stephen Liu <email@example.com> wrote:
> > As mentioned earlier in the thread, reverse proxying will let you do
> > this.
> > Just designate the one with the highest load to be the reverse proxy,
> > send
> > all traffic there, and have that proxy requests for the other server.
> > Configuration depends on the server, your setup, etc.
> Sorry I overlooked this point before. I can't figure out how to do it.
> Could you please shed me some light. Pointer would be appreciated.
if using apache2, then this  is the definitive guide to reverse proxying
(well, besides the mod_proxy documentation  itself, but it's not really
there are other proxies and web servers that can supposedly do reverse
proxying (squid, pound, lighttpd, etc), but they:
1. poorly document reverse proxying
2. seem to be more tailored towards load balancing than general reverse
proxying (or at least the documentation is)
3. are not as featureful as apache2 (rewriting links, headers, etc)
4. are not apache2 ;-) (which i was already familiar with and using for web
a reverse proxy configuration can be as simple as (assuming no rewriting):
my apache2 reverse proxy runs in a vserver guest and proxies for a bunch of
different web applications (php, python, java) and static file stores, each
in its own guest. my reverse proxy even does encryption (ssl/tls) and
compression (gzip) for all the proxied servers, because some of them don't
support those features and to centralize those features' configuration.
just some ideas to maximize your use of vservers with reverse proxying.
-- firstname.lastname@example.orgReceived on Thu Apr 24 22:18:09 2008