As far as I understand, the HTTP header cookie field, and the embedded cookie (in a URL) are case-sensitive. Is this correct?
The settings look like this:
string prefix "SESSION_ID="
On the HTTP header the cookie field looks like this:
Set Cookie: SESSION_ID=ABCDEF
But if instead of this, the request comes from a client with the cookie embedded in the url, it looks like this:
Is this field case-sensitive for the CSS? I know it is for the ACE, as I have done this and there is the "cookie secondary" command where you can specify how the url-embedded cookie looks like.
So I am afraid there is no way of making this work on a CSS?
Any help will be much appreciated!
Your config with SESSIOM_ID sent by the client gives the following debug :
JUN 2 01:33:31 3/1 49 WCC-7: CsdStickinessCheck: stickytype=3
JUN 2 01:33:31 3/1 50 WCC-7: CheckL5: cookie failback to URL, stickytype=3, pURL=8ee0e8f8
JUN 2 01:33:31 3/1 51 WCC-7: cookieStr="SESSION_ID=1234 HTTP/1.1"
JUN 2 01:33:31 3/1 52 WCC-7: strLen=24, rangeLen=24, conv=1
JUN 2 01:33:31 3/1 53 WCC-7: Prefix found: prefix="SESSION_ID="
The same config, but now the client sends session_id gives the following debug :
JUN 2 01:35:24 3/1 63 WCC-7: CheckL5: cookie failback to URL, stickytype=3, pURL=8ee058f8
JUN 2 01:35:24 3/1 64 WCC-7: cookieStr="session_id=1234 HTTP/1.1"
JUN 2 01:35:24 3/1 65 WCC-7: strLen=24, rangeLen=24, conv=1
JUN 2 01:35:24 3/1 66 WCC-7: server cookie not found. strAction=4
So, it confirms that the CSS is case sensitive.