CSS 11503 Stickyness session based

Unanswered Question
Apr 24th, 2007
User Badges:

Need assistance comming up with a soulution for session based Stickyness.

1.can this be based on the J-Session ID?

2.Can the CSS send a cookie and the clients stick to the same servers until the session expires and the cookie os removed?

3. Also can we set a timeout value for the cookie?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Syed Iftekhar Ahmed Tue, 04/24/2007 - 10:16
User Badges:
  • Blue, 1500 points or more

If servers are setting the cookies then you need something like this


Service webserver1

ip address 10.10.10.1

string server1 <-- server cookie value

active


Service webserver2

ip address 10.10.10.2

string server2 <-- server cookie value

active


Service webserver3

ip address 10.10.10.3

string server3 <-- server cookie value

active



content mycontent

vip address 12.12.12.12

add service webserver1

add service webserver2

add service webserver3

string prefix "JSESSIONID="

protocol tcp

port 80

url "/*"

advanced-balance cookies

sticky-inact-timeout 60 <-- Inactivity timeout value for cookie

active




The string prefix (that goes on the Content Rule) would need to match be the name of the

cookie string prefix "JSessionID="


Then the string on the services would need to match the value that is inserted on each

server:

Example:


Service webserver1

ip address 10.10.10.1

string server1

active



Then the cookies injected from server1 would need to look like this:

JSessionID=service1


That is how the CSS would then identify which server the cookie belongs to and how to send

it to it. If the JDSessionID values are random, then the CSS would not be able to match the values to a service.

salmodov Wed, 04/25/2007 - 20:14
User Badges:

This will only work for web traffic you can not use this for SSL traffic. CSS is unable to Decrypt the packet for inspection.

Actions

This Discussion