[Seaside] ProxyPass and the P Option

Dale Henrichs dale.henrichs at gemstone.com
Mon Nov 5 20:20:41 UTC 2007


Here are some apache conf snippets that we use for the GLASS appliance. 
We have a virtual host listening on port 80 and then virtual hosts 
sitting on ports 8081, 8082 and 8083. The loadbalancer is used to route 
requests to the virtual hosts. The path 
/opt/gemstone/apache/htdocs/glass1 resolves to a FastCGI port and host 
in our setup, so you will probably need to change that, but the real 
trick here might be 'ProxyPreserveHost' - I can't tell if you used it or 

    <VirtualHost *:80>
            ProxyPreserveHost On     #make proxy rewrite urls in the output

            ProxyPass /seaside balancer://gemtrio
            ProxyPassReverse /seaside balancer://gemtrio

            <Proxy balancer://gemtrio>
                BalancerMember http://localhost:8081/seaside
                BalancerMember http://localhost:8082/seaside
                BalancerMember http://localhost:8083/seaside

    <VirtualHost *:8081>

            DocumentRoot /opt/gemstone/apache/htdocs/glass1


Hope this helps,


Richard Eng wrote:
> I don't think I can use ProxyPass directives with Apache's mod_balancer
> load-balancing feature. Apache's balancer expects something like:
>   <Proxy balancer://seaside_cluster>
>     BalancerMember
>     BalancerMember
>     BalancerMember
>   </Proxy>
> ProxyPass directives don't seem to fit in with this.
> (I'm getting ready to explore mod_balancer. I know very little about it.)
> Richard
> ---------
> Would you care to elaborate on the reason(s) for avoiding ProxyPass?
> I also have a site with SSL that is using ProxyPass just as happily.
> John.
> Richard Eng wrote:
>> Thanks for the various configuration files. But I *am* trying to avoid using
>> ProxyPass directives, and I am not successful.
>> Apache is wickedly complicated. I think very few people actually fully
>> understand how it works. That's why there are a myriad of ad hoc
>> configurations floating throughout the Internet with users employing trial
>> and error (ie, guesswork) to adapt these configurations for their own use.
>> Consequently, these configurations are very fragile. It's a right bloody
>> mess.
>> With my configuration, I am trying to accomplish two goals:
>> 1) Secure my site with SSL.
>> 2) Load-balance my Seaside application using Apache2.
>> I've succeeded with 1), but I need to get rid of ProxyPass directives for
>> 2). My configuration, so far, is as simple as I can make it. Complex
>> configurations obfuscate the situation. Like I said, very few people really
>> understand Apache. I need to proceed very, very cautiously...
>> Richard
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list