Hi all,
I have a web cluster (2 servers so far) hosting a mixture of ASP and
ASP.NET applications, and I need session stickiness based on the cookie
for each of these two languages. ASP uses a cookie with the name
"ASPSESSIONID{some random letters}", ASP.NET uses a cookie named
"ASP.NET_SessionId". Both cookies, of course, have some random
identifier as their value.
No problem, I thought, I can just use a regexp to match the cookie name:[...]
To my delight this appears to work and saves me having to define a
separate service for each type of application; using poundctl I see this:[...]
On first glance, not knowing what to expect, it looks OK; pound is
giving me the names of the cookies. However, I notice that whenever I
look, there is only ever a single "ASP.NET_SessionId" session, which
seems a little strange.
Later, I added another service that only uses ASP.NET sessions:[...]
For that service, poundctl is currently telling me:[...]
So, it looks like, when I use a regexp to match the cookie name, pound
starts using the *name* rather than the *value* of the cookie for the
session key. This results in very unbalanced load balancing, since all
users with the same named cookie (all the ASP.NET users, in my case)
will always be assigned to a single back-end.
Is this a bug, or am I missing something here?
I'm using Dag Wieers' Pound RPM on CentOS 5:[...]
Thanks for any insight anyone can provide!
Russ
[...]
|