ACE Load Balancer and persistence reading coockie

[fabio.marino]

Hi all,

Rapid question regarding cookie stickiness.           

The ACE can read and extract/read/parse the cookie in three different way

1 ->Reading the SetCoockie message in the HTTP Response from Server to Client

2-> Reading the coockie value from the HTTP header of the client request

3-> Reading the cookie embedded in the URL string

The command sticky http-cookie name1 name2 is used for covering case 1 and 2 with name1 as the value that has to be read.

With which command can instruct the ace load balancer to read the cookie from the URL?

Do you know how is the parsing process (reading url process) in this case?

Regards,

Fabio.       

[ajayku2]

Hi,

As per the documentation:

Cookie value from the HTTP header of the client request or from the

Set-Cookie message from the server. Enter a unique identifier for the

cookie with a maximum of 64 alphanumeric characters

sticky http-cookie name1 name2

If you read the usage guidelines :

By default, the maximum number of bytes that the ACE parses to check for a cookie, HTTP header, or URL is 2048. If a cookie, HTTP header, or URL exceeds the default value, the ACE drops the packet and sends a RST (reset) to the client browser. You can increase the number of bytes that the ACE parses using the

(config-parammap-http) set header-maxparse-length

command in HTTP parameter-map configuration mode.

ACE parses to check for a cookie HTTP header, or URL is 2048  <<< This indicate that the same command is useful to read the cookie embedded in URL string.

regards,

Ajay Kumar

[fabio.marino]

Hi,

I already got the same and I reached the same intuition as you. Regarding parse of the url? This point is still open question.

Thanks for your time anyway.

Cheers.

[Cesar Roque]

Hi Fabio,

do you want to loadbalance based on the cookie or do you want to use the cookie for stickiness?

---------------------
Cesar R
ANS Team