[Seaside] ProxyPass and the P Option
boris at deepcovelabs.com
Mon Nov 5 18:49:25 UTC 2007
Except you still need ProxyPass to actually proxy, but instead of
proxying a specific host, you will proxy the cluster as you defined it,
ProxyPass / balancer://hotcluster/
BalancerMember http://184.108.40.206:8009 loadfactor=1
BalancerMember http://220.127.116.11:8009 loadfactor=2
I recall playing with this a little while ago and it seemed to be
doable, rewrites had nothing to do with it.
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
boris at deepcovelabs.com
This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of Richard Eng
> Sent: Monday, November 05, 2007 9:43 AM
> To: Seaside - general discussion
> Subject: Re: [Seaside] ProxyPass and the P Option
> I don't think I can use ProxyPass directives with Apache's
> load-balancing feature. Apache's balancer expects something like:
> <Proxy balancer://seaside_cluster>
> BalancerMember http://127.0.0.1:8000
> BalancerMember http://127.0.0.1:8001
> BalancerMember http://127.0.0.1:8002
> ProxyPass directives don't seem to fit in with this.
> (I'm getting ready to explore mod_balancer. I know very little about
> 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.
> Richard Eng wrote:
> > Thanks for the various configuration files. But I *am* trying to
> > ProxyPass directives, and I am not successful.
> > Apache is wickedly complicated. I think very few people actually
> > understand how it works. That's why there are a myriad of ad hoc
> > configurations floating throughout the Internet with users employing
> > and error (ie, guesswork) to adapt these configurations for their
> > Consequently, these configurations are very fragile. It's a right
> > 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
> > 2). My configuration, so far, is as simple as I can make it. Complex
> > configurations obfuscate the situation. Like I said, very few people
> > understand Apache. I need to proceed very, very cautiously...
> > Richard
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside