You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the following annotations in voyager ingress settings, when we set the 'session-cookie-name' as any string, say abc (anuthing other than SERVERID) , we notice that client is sending the 'abc' cookie in request (seen in fiidler), but server is not receiving the cookie (as evident from application server-logs). And the .jnlp file, (returned from the server) does not have abc cookie mentioned.
Due to this, we find that sticky session is not working as expected in case of jnlp applet.
Note: we have not encountered this issue with other load-balancers with everything else being exactly same ..
The text was updated successfully, but these errors were encountered:
With the following annotations in voyager ingress settings, when we set the 'session-cookie-name' as any string, say
abc
(anuthing other thanSERVERID
) , we notice that client is sending the 'abc' cookie in request (seen in fiidler), but server is not receiving the cookie (as evident from application server-logs). And the .jnlp file, (returned from the server) does not haveabc
cookie mentioned.annotations:
ingress.appscode.com/type: 'NodePort'
ingress.appscode.com/stats: 'true'
ingress.appscode.com/affinity: 'cookie'
ingress.appscode.com/session-cookie-name: abc
Due to this, we find that sticky session is not working as expected in case of jnlp applet.
Note: we have not encountered this issue with other load-balancers with everything else being exactly same ..
The text was updated successfully, but these errors were encountered: