[
https://issues.apache.org/jira/browse/KNOX-3033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17844707#comment-17844707
]
Istvan Toth commented on KNOX-3033:
-----------------------------------
I don't understand the code enough to tell if it is possible, but ideally we
should set the proper context (the context of the public URI for the service)
on the cookie.
I.e. for the above example for WEBHBASE, it should be set to
/gateway/cdp-proxy-api-stoty/hbase
> the service name is appended to explicitly set stickySessionCookieName
> ----------------------------------------------------------------------
>
> Key: KNOX-3033
> URL: https://issues.apache.org/jira/browse/KNOX-3033
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Istvan Toth
> Priority: Major
>
> I have tried to override the sticky session cookie name by using the
> following HA parameter:
> {noformat}
> <param>
> <name>WEBHBASE</name>
>
> <value>enableStickySession=true;noFallback=true;enableLoadBalancing=true;stickySessionCookieName=STICKYCOOKIE</value>
> </param>
> {noformat}
> However, KNOX still appended the service name to the cookie name:
> {noformat}
> 24/04/30 08:25:11 DEBUG http.wire: http-outgoing-0 << "Set-Cookie:
> STICKYCOOKIE-WEBHBASE=58d004bcaccfddfdc69739ea053505c69b2679d6fc1da6f7e46d3907be2d1e6c;
> Path=/gateway/cdp-proxy-api-stoty; Secure; HttpOnly[\r][\n]"
> {noformat}
> AFAICT the point of overriding the cookie name would be integrating with
> other components (like a cloud LB) that expect a specific cookie name.
> Appending the service name after the specified cooke name defeats this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
