Re: [summary] Re: front end proxy and virtual hosts

2000-04-17 Thread Vivek Khera
Looks good; I'd recommend keeping *.html files on the front-end as well, since they tend to be static, and also any traditional *.cgi since they don't need mod_perl's bloat on the fork/exec. Also, specifying "Port 80" inside each virtual on the back-end is not necessary, though perhaps setting a

Re: front end proxy and virtual hosts

2000-04-15 Thread Matt Carothers
On Mon, 10 Apr 2000, Eric Cholet wrote: The front-end light server, serving static requests and proxying dynamic requests to a back-end modperl server, is well documented, except in the case of virtual hosts. How do you do it? On the front end: VirtualHost www.customer.com

[summary] Re: front end proxy and virtual hosts

2000-04-15 Thread Stas Bekman
=head1 Front-end Back-end Proxying with Virtual Hosts This section explains a configuration setup for proxying your back-end mod_perl servers when you need to use Virtual Hosts. The approach is to use unique port number for each virtual host at the back-end server, so you can redirect from the

RE: front end proxy and virtual hosts

2000-04-13 Thread Eric Cholet
This leads me to believe that the Rewrite engine is ignored when an Alias kicks in, otherwise the *.shtml files would be bounced back to the back-end server where they get properly expanded. Normally, this is ok for me since everything else in the aliased directory is an image which I want

Re: front end proxy and virtual hosts

2000-04-12 Thread Ask Bjoern Hansen
On Mon, 10 Apr 2000, Eric Cholet wrote: Port based backend servers is the easiest. Use Port 80 Listen 127.0.0.1:8088 (or whatever) Listen 127.0.0.1:8089 ... in your backend setup to make sure it never reveals the real port and only listens on the loopback interface (if that's what you want).

Re: front end proxy and virtual hosts

2000-04-12 Thread Vivek Khera
I just ran into a bit of a conflict with Alias and Rewrite on my front end. Given that I have multiple virtual hosts serving up the same content using a slightly different set of graphics and templates, the easy way is to "Alias /_pageparts /real/page/parts/directory" and make the alias

Re: front end proxy and virtual hosts

2000-04-12 Thread Ask Bjoern Hansen
On Wed, 12 Apr 2000, Vivek Khera wrote: [...] Has this bitten anyone else? Stas, I think you should mention this in the guide somehow as something to watch out for when using the proxy front-end. The Rewrite rules are ignored when an Alias expands the URI, or so it seems from where I sit.

Re: front end proxy and virtual hosts

2000-04-12 Thread Vivek Khera
"ABH" == Ask Bjoern Hansen [EMAIL PROTECTED] writes: ABH mod_alias does - (except for ScriptAlias which is not really relevant on Duh. Ya know, sometimes you stare and stare and stare and it doesn't come to you. I don't even need mod_alias at all... Thanks!

Re: front end proxy and virtual hosts

2000-04-10 Thread Vivek Khera
"EC" == Eric Cholet [EMAIL PROTECTED] writes: EC do you setup virtual hosts on the backend server? Different IPs, or EC different ports? Or just a flat url space, using mod_rewrite on the EC front-end to translate the urls? I think I posted this example earlier. This is just a snippet of the

RE: front end proxy and virtual hosts

2000-04-10 Thread Eric Cholet
EC do you setup virtual hosts on the backend server? Different IPs, or EC different ports? Or just a flat url space, using mod_rewrite on the EC front-end to translate the urls? I think I posted this example earlier. This is just a snippet of the relevant portions of the front/back end

Re: front end proxy and virtual hosts

2000-04-10 Thread Tom Mornini
On Mon, 10 Apr 2000, Eric Cholet wrote: The front-end light server, serving static requests and proxying dynamic requests to a back-end modperl server, is well documented, except in the case of virtual hosts. How do you do it? Specifically, do you setup virtual hosts on the backend server?