httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Plüm, Rüdiger, VF-Group <ruediger.pl...@vodafone.com>
Subject AW: Bug 41897 / Session-Stickiness with mod_proxy_balancer
Date Tue, 08 May 2007 09:47:17 GMT


> -----Ursprüngliche Nachricht-----
> Von: Georg von Zezschwitz 
> Gesendet: Dienstag, 8. Mai 2007 10:05
> An: dev@httpd.apache.org
> Betreff: Re: Bug 41897 / Session-Stickiness with mod_proxy_balancer
> 

> You declare a balancer:
> 
> <Proxy balancer://mycloud>
>   BalancerMember ajp://192.168.1.1:5001 route=member1
>   BalancerMember ajp://192.168.1.2:5001 route=member2
> </Proxy>
> 
> Now I want to balance 2 paths:
> 
> <Location /app1>
>   ProxyPass balancer://mycloud/app1 stickysession=JSESSION
> </Location>
> 
> <Location /app2>
>   ProxyPass balancer://mycloud/app2 stickysession=JSESSION
> </Location>
> 
> The repeated ProxyPass definitions might give the impression that you 
> can specify
> different settings for /app1 and /app2 - e.g. stickysession 
> parameters 
> (which is not true).
> 
> Using an elegant:
> 
> <LocationMatch "/(app1|app2)">
> 
> is also not possible if the path element (/app1 vs /app2) has to be 
> passed to the backend.

What about this?

RewriteRule ^/(app1|app2)(.*) balancer://mycloud/$1$2 [P]

<Proxy balancer://mycloud>
   BalancerMember ajp://192.168.1.1:5001 route=member1
   BalancerMember ajp://192.168.1.2:5001 route=member2
   ProxySet stickysession=JSESSION
</Proxy>

Hint: You may need to apply the following patch from trunk to get this working:

http://svn.apache.org/viewvc?view=rev&revision=427920



Regards

Rüdiger

Mime
View raw message