How LTM attaches information about node to JSessionsID ?

Hi Christian,

 

We have universal and cookie because:

 

iRULE - uie

 

virtual - cookie

 

Virtual server configuration:

 

ltm virtual PI-SSL {

 

destination 10.59.20.10:https

 

fallback-persistence PI_Tomcat-src

 

ip-protocol tcp

 

mask 255.255.255.255

 

persist {

 

PI_COOKIE {

 

default yes

 

}

 

}

 

pool SRV_POOL

 

profiles {

 

PI-HTTPS-NEW.app/PI-HTTPS-NEW_http_profile { }

 

PI-HTTPS-NEW.app/PI-HTTPS-NEW_lan-optimized_tcp_profile {

 

context serverside

 

}

 

PI-HTTPS-NEW.app/PI-HTTPS-NEW_oneconnect { }

 

PI-HTTPS-NEW.app/PI-HTTPS-NEW_wan-optimized_tcp_profile {

 

context clientside

 

}

 

PI-requestLog { }

 

PI_SSL {

 

context clientside

 

}

 

analytics { }

 

}

 

rules {

 

PI_X-Forward

 

PI_JSESSION_ID

 

}

 

snat automap

 

source-port change

 

vlans-disabled

 

}

 

IRULE:

 

when HTTP_REQUEST {

 

if { [HTTP::cookie exists "JSESSIONID"] } {

 

persist uie [HTTP::cookie "JSESSIONID"] 500

 

} else {

 

set jsess [findstr [HTTP::uri] "JSESSIONID" 11 ";"]

 

if { $jsess != "" } {

 

persist uie $jsess 500

 

}

 

}

 

}

 

when HTTP_RESPONSE {

 

if { [HTTP::cookie exists "JSESSIONID"] } {

 

persist add uie [HTTP::cookie "JSESSIONID"] 500

 

}

 

}