Curl thinks it's being set:
< HTTP/1.1 200 OK
< Server: Apache-Coyote/1.1
< Set-Cookie: JSESSIONID=7B26C0CAABC706C1942ACF4187FD0608; Path=/path;
HttpOnly
< P3P: CP='IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND
CNT TST'
< Cache-Control: no-store
< Pragma: no-cache
< Expires: -1
Interesting - the vendor didn't notify us about such a change. I'll have
to investigate.
Simon
On 27/04/18 10:59, Maximilian Boehm wrote:
Hi,
Sessions are managed on haproxy with a stick table which stores a JSESSIONID
Just to make sure: Are you sure this application still uses JSESSIONID
N¬Æ§Kó0K"wë,j
Qv /vç<ïÀ¸è?Cӽ¯5à-S¢©®r~æ[±¢¸!jèÇ'è®h¥»++ç-bèiÖÚ©Üx²)àêZ橦Xjب6xZâÛ°)¯m5óOy÷MþÓM4
íz{Kjx.jx1¢{^Ôò¥ë^Æß騧r«±ë
3 matches
Mail list logo
