If I am looking at it correctly the order of the ProxyPass directives you defined is not the correct one, /sz defined first would be overriding /sz2. So sz2 should be defined first.
Perhaps that's why you are getting wrong values ? (Browser cache or similar?) El mar., 15 jun. 2021 19:00, Nick Folino <n...@folino.us> escribió: > I ran into an interesting situation with cookies being reset in balancers. > I couldn't find any documentation on whether numbers are allowed in > balancer names. > > I have this config: > > <Proxy balancer://rz> > Header add Set-Cookie "RZROUTEID=.%{BALANCER_WORKER_ROUTE}e; path=/" > env=BALANCER_ROUTE_CHANGED > BalancerMember ajp://server1 route=01 > BalancerMember ajp://server2 route=02 > ProxySet stickysession=RZROUTEID > </Proxy> > > <Proxy balancer://rz2> > Header add Set-Cookie "RZ2ROUTEID=.%{BALANCER_WORKER_ROUTE}e; > path=/" env=BALANCER_ROUTE_CHANGED > BalancerMember ajp://server3 route=03 > BalancerMember ajp://server4 route=04 > ProxySet stickysession=RZ2ROUTEID > </Proxy> > > ProxyPass /rz balancer://rz/rz > ProxyPass /rz2 balancer://rz2/rz2 > > > All works as expected when going to http://myhost/rz > I get the RZROUTEID cookie set to 01 or 02 on first hit and it stays set. > > If I then go to http://myhost/rz2 I get the RZ2ROUTEID set to 03 or 04 > but also another cookie set for RZROUTE with the same value as the > RZ2ROUTEID cookie. > > This causes an issue when going back to /rz as the RZROUTEID cookie is now > invalid and gets reset based on the balancing rules. > > I solved the problem by renaming the rz2 balancer to a new name with a > digit. > Is this by design that digits cause problems in balancer names? or is > this a bug? > > Nick > >