<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] ProxyPass and the P Option</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>You could add route identifying cookie to each app, say its hostname plus port number although I recall seeing solutions to use mod balancer without modding existing apps with mod_headers, google some.<BR>
<BR>
<BR>
Cheers!<BR>
<BR>
-Boris<BR>
(Sent from a BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Tue Nov 06 06:28:51 2007<BR>
Subject: Re: [Seaside] ProxyPass and the P Option<BR>
<BR>
I guess I can do something like this:<BR>
<BR>
<VirtualHost 192.168.1.101:443><BR>
RewriteEngine on<BR>
ProxyRequests off<BR>
ProxyPreserveHost on<BR>
SSLEngine on<BR>
SSLCertificateFile /etc/apache2/ssl/apache.pem<BR>
DocumentRoot /var/www/ssl<BR>
ProxyPass /seaside/go balancer://seaside_cluster<BR>
stickysession=MYCOOKIE nofailover=on<BR>
ProxyPassReverse /seaside/go balancer://seaside_cluster<BR>
<Proxy balancer://seaside_cluster><BR>
BalancerMember <A HREF="http://localhost:9090/seaside/go">http://localhost:9090/seaside/go</A> route=A_<BR>
BalancerMember <A HREF="http://localhost:9091/seaside/go">http://localhost:9091/seaside/go</A> route=B_<BR>
BalancerMember <A HREF="http://localhost:9092/seaside/go">http://localhost:9092/seaside/go</A> route=C_<BR>
</Proxy><BR>
RewriteRule ^/$ balancer://seaside_cluster [P,L]<BR>
</VirtualHost><BR>
<BR>
<BR>
Apparently, the format of the cookie name is something like<BR>
'somename.someroute'. I think in the above example, somename would be<BR>
MYCOOKIE and someroute would be A_ or B_ or C_. Am I understanding<BR>
correctly?<BR>
<BR>
But do I need to setup cookies in Seaside? If so, do I need to setup the<BR>
cookie name format, as well? If so, how?<BR>
<BR>
Thanks,<BR>
Richard<BR>
<BR>
--------<BR>
How do you ensure session affinity?<BR>
<BR>
It looks like you are using a round-robin strategy. I guess this is<BR>
what Apache does by default. You have to ensure that only the first<BR>
request goes to a random image, subsequent requests should go to the<BR>
same image.<BR>
<BR>
Lukas<BR>
<BR>
<BR>
_______________________________________________<BR>
seaside mailing list<BR>
seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>