LocalDirector 417 and JSESSIONID url argument

[nickpiper]

I am installing a LD417 in front of a cluster of WebLogic servers.

The LD417 will passively inspect the JSESSIONID cookie in order to keep the connections from a particular client going to the same WebLogic server (WLS). If that WLS goes down, it will send on to a different server, and the new WLS will request the session information from whichever WLS has the backup.

Some times the client device might not support cookies, in which case the WLS will use url rewriting (appending ;JSESSIONID=A6B2... to the url) instead. Can the LD417 use this url argument as a key for stickiness, instead of the cookie? Quite a lot of documentation hints to this possibility, but I have not found anything concrete.

Thanks,

Nick

[thamdani]

Hi Nick,

LD is not capable of doing what you want to accomplish .Sticky based on cookie in url.The LD scans the HTTP GET request for a cookie (cookie-passive) it cannot scan the URL for cookie .

The Content service switch (CSS) which is the advanced Load balancer can handle this .

Tanveer