[jira] [Updated] (KNOX-2946) Cookie Path Scoping doesn't work when using default topology URL
[ https://issues.apache.org/jira/browse/KNOX-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated KNOX-2946: Fix Version/s: 2.1.0 > Cookie Path Scoping doesn't work when using default topology URL > > > Key: KNOX-2946 > URL: https://issues.apache.org/jira/browse/KNOX-2946 > Project: Apache Knox > Issue Type: Bug >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > Fix For: 2.1.0 > > Time Spent: 40m > Remaining Estimate: 0h > > When gateway.scope.cookies.feature.enabled is turned on, knox will update the > Path attribute of the Set-Cookie header to /ctxpath/topology_name/, e.g.: > Original: > Set-Cookie: xxx Path = / > Updated: > Set-Cookie: xxx Path = /gateway/cdp-proxy > However, when the gateway.default.app.topology.name is set to cdp-proxy, and > we access a service via the default topology (there is no cdp-proxy in the > URL) then the cookie will be blocked by the browser. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KNOX-2946) Cookie Path Scoping doesn't work when using default topology URL
[ https://issues.apache.org/jira/browse/KNOX-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated KNOX-2946: Description: When gateway.scope.cookies.feature.enabled is turned on, knox will update the Path attribute of the Set-Cookie header to /ctxpath/topology_name/, e.g.: Original: Set-Cookie: xxx Path = / Updated: Set-Cookie: xxx Path = /gateway/cdp-proxy However, when the gateway.default.app.topology.name is set to cdp-proxy, and we access a service via the default topology (there is no cdp-proxy in the URL) then the cookie will be blocked by the browser. was: When gateway.scope.cookies.feature.enabled is turned on, knox will update the Path attribute of the Set-Cookie header to /ctxpath/topology_name/, e.g.: Original: Path = / Updated: Path = /gateway/cdp-proxy However, when the gateway.default.app.topology.name is set to cdp-proxy, and we access a service via the default topology (there is no cdp-proxy in the URL) then the cookie will be blocked by the browser. > Cookie Path Scoping doesn't work when using default topology URL > > > Key: KNOX-2946 > URL: https://issues.apache.org/jira/browse/KNOX-2946 > Project: Apache Knox > Issue Type: Bug >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > > When gateway.scope.cookies.feature.enabled is turned on, knox will update the > Path attribute of the Set-Cookie header to /ctxpath/topology_name/, e.g.: > Original: > Set-Cookie: xxx Path = / > Updated: > Set-Cookie: xxx Path = /gateway/cdp-proxy > However, when the gateway.default.app.topology.name is set to cdp-proxy, and > we access a service via the default topology (there is no cdp-proxy in the > URL) then the cookie will be blocked by the browser. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KNOX-2946) Cookie Path Scoping doesn't work when using default topology URL
[ https://issues.apache.org/jira/browse/KNOX-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated KNOX-2946: Description: When gateway.scope.cookies.feature.enabled is turned on, knox will update the Path attribute of the Set-Cookie header to /ctxpath/topology_name/, e.g.: Original: Path = / Updated: Path = /gateway/cdp-proxy However, when the gateway.default.app.topology.name is set to cdp-proxy, and we access a service via the default topology (there is no cdp-proxy in the URL) then the cookie will be blocked by the browser. was: When gateway.scope.cookies.feature.enabled is turned on, knox will update the Path attribute of the Set-Cookie header to /ctxpath/topology_name/, e.g.: Original: Path = / Updated: Path = /gateway/cdp-proxy However, when the gateway.default.app.topology.name is set to cdp-proxy, an we access a service via the default topology (there is no cdp-proxy in the URL) then the cookie will be blocked by the browser. > Cookie Path Scoping doesn't work when using default topology URL > > > Key: KNOX-2946 > URL: https://issues.apache.org/jira/browse/KNOX-2946 > Project: Apache Knox > Issue Type: Bug >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > > When gateway.scope.cookies.feature.enabled is turned on, knox will update the > Path attribute of the Set-Cookie header to /ctxpath/topology_name/, e.g.: > Original: > Path = / > Updated: > Path = /gateway/cdp-proxy > However, when the gateway.default.app.topology.name is set to cdp-proxy, and > we access a service via the default topology (there is no cdp-proxy in the > URL) then the cookie will be blocked by the browser. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (KNOX-2946) Cookie Path Scoping doesn't work when using default topology URL
[ https://issues.apache.org/jira/browse/KNOX-2946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Magyar updated KNOX-2946: Summary: Cookie Path Scoping doesn't work when using default topology URL (was: Cookie Scoping doesn't when using default topology URL) > Cookie Path Scoping doesn't work when using default topology URL > > > Key: KNOX-2946 > URL: https://issues.apache.org/jira/browse/KNOX-2946 > Project: Apache Knox > Issue Type: Bug >Reporter: Attila Magyar >Assignee: Attila Magyar >Priority: Major > > When gateway.scope.cookies.feature.enabled is turned in, knox will update the > Path attribute of the Set-Cookie header to /ctxpath/topology_name/, e.g.: > Original: > Path = / > Updated: > Path = /gateway/cdp-proxy > However, when the gateway.default.app.topology.name is set to cdp-proxy, an > we access a service via the default topology (there is no cdp-proxy in the > URL) then the cookie will be blocked by the browser. -- This message was sent by Atlassian Jira (v8.20.10#820010)
