https://bz.apache.org/bugzilla/show_bug.cgi?id=62998
--- Comment #4 from Ruediger Pluem <[email protected]> --- (In reply to Vipin Pillai from comment #3) > HI ERIC and Ruediger, > > Thanks for your inputs. > > I have changed configuration to > > ProxyRequests On > > Header add Set-Cookie "ROUTEID=.%{BALANCER_WORKER_ROUTE}e; Path=/; HttpOnly" > env=BALANCER_ROUTE_CHANGED > > <Proxy "balancer://TomcatCluster"> > > BalancerMember "ajp://abc.com:8009" route=worker1 KeepAlive=On > > BalancerMember "ajp://xyz.com:8009" route=worker2 KeepAlive=On > > ProxySet stickysession=ROUTEID > > ProxySet lbmethod=bybusyness > > </Proxy> > > ProxyPass / "balancer://TomcatCluster/" stickysession=ROUTEID > > ProxyPassReverse / "balancer://TomcatCluster/" > > #ProxyPassReverseCookiePath balancer://TomcatCluster/ / > > ProxyTimeout 1200000 > > KeepAlive On > > KeepAliveTimeout 60 > > MaxKeepAliveRequests 100 > > and I have set log format iin httpd.conf as below > > LogFormat > "%h;%t;%r;%>s;%b;%{Referer}i;%{User-Agent}i;%{JSESSIONID}C;%{ROUTEID}C; > %{BALANCER_SESSION_STICKY}e;%{BALANCER_SESSION_ROUTE}e; > %{BALANCER_WORKER_ROUTE}e" accessLog > > Still the issues is same and in logs I am getting same issues for ROUTEID > > <ip>;[11/Dec/2018:04:18:32 +0000];GET > /biprws/internal/v1/settings/userpreferences/ > pagepreferences?pagesize=50&_=1544501910008 > HTTP/1.1;200;114;https://loadbalancer.com > /BOE/portal/1810011833/FioriBI/main.jsp?service=%2Fcommon%2FappService. > do&appKind=InfoView;Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; > rv:11.0) like Gecko;-;.worker2;-;-;worker2 > > For JESSIONID and getting proper values for BALANCER_SESSION_STICKY and > BALANCER_SESSION_ROUTE in logs as below > > <ip>;[11/Dec/2018:04:18:31 +0000];GET > /BOE/portal/1810011833/FioriBI/i18n/fioribiResources_en_GB.properties > HTTP/1.1;404;2497;https://loadbalancer.com/BOE/portal/1810011833/FioriBI/ > main.jsp?service=%2Fcommon%2FappService.do&appKind=InfoView;Mozilla/5.0 > (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like > Gecko;E6B65125A368F523379AE2DE134F4B1C.worker1;.worker2;JSESSIONID;worker1; > worker1 The logs show that the JSESSIONID cookie is used to extract the routing information and not the ROUTEID cookie. So it is likely that the configuration you supplied above is not the one that was used when the log entries were written. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
