Forum Discussion
Davo_T_20783
Nimbostratus
Looks like it may be an APM problem. Support ticket raised with F5 and issue has been reproduced, now waiting for further investigation.
daboochmeister
Feb 12, 2015Cirrus
Has there been further news on this? I appear to be experiencing the same issue ... though in our case, the JSESSIONID doesn't make it to the client even if we have a basically empty APM policy, no kerberos, not even any authentication involved. In fact, we go through 2 layers of F5 - an external tier running APM which proxies to an internal F5, which proxies to the real servers - and the JSESSIONID is in fact returned by the internal F5, it gets swallowed by the external F5 running APM, apparently.