Yann,
We found it by user complaints. Digging into the complaints, it was
determined by watching the headers what was happening. Then just a lucky
guess as to why it was happening helped us resolve it.
Nick
On Fri, Jun 18, 2021 at 4:36 AM Yann Ylavic <ylavic....@gmail.com> wrote:
> Hi Daniel,
>
> How do you monitor this, but looking at the request Cookie header sent
> by the browser or the Set-Cookie sent by httpd?
>
> >> >>
> >> >> <Proxy "balancer://rz">
> >> >> Header add Set-Cookie "RZROUTEID=.%{BALANCER_WORKER_ROUTE}e;
> path=/" env=BALANCER_ROUTE_CHANGED
>
> What if you configure "path=/rz" here ...
>
> >> >> BalancerMember http://www.google.com route=01
> >> >> BalancerMember http://www.yahoo.com route=02
> >> >> ProxySet stickysession=RZROUTEID
> >> >> </Proxy>
> >> >> <Proxy "balancer://rz2">
> >> >> Header add Set-Cookie "RZ2ROUTEID=.%{BALANCER_WORKER_ROUTE}e;
> path=/" env=BALANCER_ROUTE_CHANGED
>
> And "path=/rz2" here ?
>
> >> >> BalancerMember http://www.fox.com route=03
> >> >> BalancerMember http://www.cnn.com route=04
> >> >> ProxySet stickysession=RZ2ROUTEID
> >> >> </Proxy>
>
>
> Regards;
> Yann.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>
