topic Re: ACE Cookie Persistence in Application Networking

ACE Cookie Persistence

kris-andrews — Wed, 22 Sep 2010 09:58:06 GMT

Hi All,

I have an issue on the ACE that is doing SSL offload to a server farm and using cookies for stickyness.

The issue is I am trying to establish what value i need to enter when trying to dynamically learn cookies in the server response?

I understand that cookie insertion is an option but is not currently being used.

I have checked the syntax

sticky http-cookie

name1 name2

Where name1 is the value that needs to be matched, how do i find out this value?

Your help would be much appreciated.

Kris

Re: ACE Cookie Persistence

litrenta — Wed, 22 Sep 2010 12:31:24 GMT

You need to find out from the application developer what the name of the cookie

is. The server responds with a set-cookie header with name

=value . We need to find out from the server what cookie name we want to stick on.

Re: ACE Cookie Persistence

kris-andrews — Fri, 24 Sep 2010 08:19:48 GMT

Thanks litrenta,

So on further investigation i have been told the value to match is sessionid, apparently there are different values depending on the application. So in this instance if the application is microsoft is there a certain sessionid value to be matched?

I'm still a little confused as to what needs to be entered, this isn't something that i have come accross before.

Kris

Re: ACE Cookie Persistence

Gilles Dufour — Fri, 24 Sep 2010 12:13:12 GMT

Kris,

that a sniffer trace of the traffic going to the server.

Then check the server response for a line which looks like : set-cookie: name=value.

This means the server will always use the cookie "name" and a different "Value" for each client.

So you configure ACE to look for hte "name" and it will learn the "value" automatically.

If you really do not understand http cookies, you could simply use the "sticky cookie insert" feature.

ACE will do everything for you automatically.

Gilles.

Re: ACE Cookie Persistence

arthurlove — Tue, 28 Sep 2010 06:27:36 GMT

..or you could use

http-fox with firefox - this will show you the cookies being served out.

you may also have to use parameter-map type [eg] http MAP_NAME

case-insensitive

but over all life is simpler using the cookie insert feature