Re: Apache delegation

On 7/1/2011 6:51 AM, Samir Faci wrote:
> This is what I'm trying to do.... and let me know if its easily possible or not.
>
>
>
> big puffy internet cloud -->    * DD-WRT *   -->
> VirtualMachineServer--->|  .101 ->  webapp1   .102 -->  redmine  .103 ->
> joomla    |
>
> Lets say domain = candy.com
>
> so.. what I was thinking of doing is having a dedicated to various
> tasks like a mysql.candy.com  which isn't a big deal since
> I don't need that publicly accessible, ldap isn't an issue.. but if I
> want to host different web apps on different machines..
>
> I know I can do www.candy.com:80 == webapp1   www.candy.com:81 ==
> redmine   but that's messy....
>
> I wanted to setup an apache server that everything hits, that then
> forwards the queries to the appropriate one.. that renders or
> does what it needs to do.. and then retrieves the data and sends it
> back to client.  ie.  excuse my bad ascii art.
>
> a request would go something like....
>
>
> user1 type redmine.candy.com ---->  wanIP -->  firewall-->master
> apache..  *oh, redmine is my .102 address *  -->   redmine apache
> *process.. do stuff return results to master apache -->  master apache
> return result to user1.
>
> I'm trying to create what would normally be an apache cluster or some
> form, but with only one public IP, so I'm wondering if anyone had any
> thoughts if this was possible or how to accomplish this.

	I use Varnish to reverse proxy other machines, but you could use Squid, 
Apache, Nginx, or any other reverse proxy. You may need to enable extra 
modules in you Apache config like expires and headers on the Apache 
servers you're proxying to control TTL or read x-forwarded-for headers. 
  Most of the time you can toss in a reverse proxy and everything just 
works, but there are times it can require a bit of thought.

Ramin
-- 
Linux Users Of Northern Illinois (Chicago) - Technical Discussion 
http://luni.org/mailman/listinfo/luni