Forum OpenACS Q&A: Reverse proxy for multi domain

Collapse
1: Reverse proxy for multi domain
Posted by jack hewa on 08/02/07 03:01 AM
Hi All,

I have Oracle Http Apache server setup as reverse proxy for our main web sites. Now just want to use the same reverse proxy server for other web sites which are not part of the main web site. Apache virtual host configuration only allows to specify ip address and this servers ip address has been configured for our manin web sites. Could someone please suggest how to do this?

Thanks in advance,

Jack

Collapse
2: Re: Reverse proxy for multi domain (response to 1)
Posted by Malte Sussdorff on 08/02/07 10:09 AM
Sadly no answer to your question, but you should read up on NGINX to achieve the same result in case you will not find the answer: http://cognovis.de/developer/en/nginx_overview
Collapse
3: Re: Reverse proxy for multi domain (response to 2)
Posted by Jon Griffin on 08/05/07 03:35 AM
Malte,
I just got rid of my squid cache and wonder if the following might work?

I have nginx running on my firewall but have several servers that host sites. Everything works fine, but I would like to cache the static content which I can't do because the content is not local.

I probably need nginx forwarding to nginx on the local machine. The problem is this is a live setup so I don't want to screw around to much.

I do have to say, it is much better than squid. And I never could get pound to work right. This was easy.

Collapse
4: Re: Reverse proxy for multi domain (response to 3)
Posted by Malte Sussdorff on 08/05/07 09:11 AM
For resources I just copy them over, so everything under $package/resources comes on the NGINX server under /web/resources/$package and NGINX is configured to get it from there.

For static content that resides in /www, you can mount those directories via NFS and have NGINX pull it from there, or, alternatively, and much better if you do not change static files often, run RSYNC on a regular basis.

I would not recommend setting up a local NGINX for the static files, as you loose the benefit of not having to pull the files from the server running AOLserver.

Also be aware that a good practice for me was to use NGINX for SSL and not AOLserver (reduces load on the NSD process).

And you can do reverse proxy based on URL, which means you can run part of the URL (e.g. like /image, /file, /shared/portrait-bits) from an AOLserver just used for CR File distribution.

Collapse
5: Re: Reverse proxy for multi domain (response to 1)
Posted by jack hewa on 08/07/07 03:20 AM
Thanks Malte for your reply.