Solved: ACE Cookie insert behavior

parveesm123 · ‎04-08-2012

Hi ,

My requirement is as follows

i have following url

http://x.x.x.x/abc

http://x.x.x./dce

http://x.x.x.x/fgh

only for http://x.x.x.x/abc should be using stickiness based on http cookie insert remaining all it should use ip based stickiness.

problem what i am facing is ,

if i access http://x.x.x.x/dce , it is not showing any COOKIE in the header ( which is as expected ) and when i access http://x.x.x./abc it showing the inserted COOKIE (again expected) , but when i am accessing the url http://x.x.x.x/dce or fgh again , it is still showing the INSERTED COOKIE is it a known behaviour?.

as far as i understand , before the session request , ACE maintains the insert cookie values in the cookie database and thus it is less processing intensive.

However , why is it inserting to all request , even though i am not configuring as such .

following is my configuration , is it a known behaviour or is it the way it should work?

serverfarm host SF-FOR-DCE

probe TCP_8032

rserver MYSERVER1 8032

inservice

rserver MYSERVER2 8032

inservice

serverfarm host SF-FOR-FGH

probe TCP_8083

rserver MYSERVER1 8083

inservice

rserver MYSERVER2 8083

inservice

serverfarm host SF-FOR-ABC

probe TCP_8081

rserver MYSERVER1 8081

inservice

rserver MYSERVER1 8081

inservice

sticky http-cookie COOKIE-SKYCHAIN STICKY-ABC

cookie insert browser-expire

timeout 720

replicate sticky

serverfarm SF-FOR-ABC

sticky ip-netmask 255.255.255.0 address source STICKY-DCE

timeout 720

replicate sticky

serverfarm SF-FOR-DCE

sticky ip-netmask 255.255.255.0 address source STICKY-EFG

timeout 720

replicate sticky

serverfarmSF-FOR-FGH

class-map type http loadbalance match-all CM7-1

2 match http url /dce/*.*

class-map type http loadbalance match-all CM7-2

2 match http url /fgh/*.*

class-map type http loadbalance match-all CM7-3

2 match http url /abc*.*

policy-map type loadbalance first-match PM7-1

class CM7-1

sticky-serverfarm STICKY-DCE

class CM7-2

sticky-serverfarm STICKY-EFG

class CM7-3

sticky-serverfarm STICKY-ABC

class-map match-any CM3-VIP

3 match virtual-address x.x.x.x tcp eq www

policy-map multi-match PM34-VIP

class CM3-VIP

loadbalance vip inservice

loadbalance policy PM7-1

loadbalance vip icmp-reply

Assistance appreciated.

thanks

-PMD

jsirstin · ‎04-09-2012

Are you seeing the client still send the cookie when going to the other locations /DCE or /FGH, or are you seeing the ACE insert the cookie? If you are only seeing the client still sending the cookie this is expected behavior. The cookie is issued for the path / so if the client learned the cookie from the domain x.x.x.x it will send the cookie any time it goes to that domain regardless of the path that is being used.

Regards

Jim

View solution in original post

gaursin2 · ‎04-08-2012

Hi

you are missing 'persistence rebalance' parameter-map in your confiugration. This parameter-map will tells ACE to inspect every request of a TCP connection

try that........

parveesm123 · ‎04-09-2012

Hi GS,

Nopes it didnt helped

- PMD

jsirstin · ‎04-09-2012

Are you seeing the client still send the cookie when going to the other locations /DCE or /FGH, or are you seeing the ACE insert the cookie? If you are only seeing the client still sending the cookie this is expected behavior. The cookie is issued for the path / so if the client learned the cookie from the domain x.x.x.x it will send the cookie any time it goes to that domain regardless of the path that is being used.

Regards

Jim

Borys Berlog · ‎04-11-2012

As Jim wrote , it's correct behavior, but it shouldn't cause any inconveniences for you, as for /dce and /fgh cookies are not checked (those requests are coming to different sticky groups as per your config), so only "problem" you should have is that HTTP header will contain one extra cookie.

parveesm123 · ‎04-11-2012

Thanks Jim,

Its clear now.. Appreciate :-)

cheers

-PMD