[
https://issues.jboss.org/browse/WFLY-5012?page=com.atlassian.jira.plugin....
]
Kabir Khan commented on WFLY-5012:
----------------------------------
Another part of this, is that there is nothing in r-r-d's output indicating that this
is an alias. So perhaps that is needed, and if something is an alias, should we put in
both the 'real' and 'alias' addresses?
Resource alias operation inconsistencies
----------------------------------------
Key: WFLY-5012
URL:
https://issues.jboss.org/browse/WFLY-5012
Project: WildFly
Issue Type: Bug
Components: Domain Management
Reporter: Heiko Braun
Assignee: Kabir Khan
Priority: Blocker
Fix For: 10.0.0.Beta1
Formlery we could request the ../eviction=EVICTION resource. I assume that with the
resource name change a transformer kicks that redirects the request to the
../component" => "eviction resource. The response header however contains the
wrong address, which prevents clients to correlate the request with the response.
*In HAL this breaks the access control mechanism.*
{noformat}
[domain@localhost:9990 /]
/profile=full/subsystem=infinispan/cache-container=*/invalidation-cache=*/eviction=EVICTION:read-resource-description
{
"outcome" => "success",
"result" => [{
"address" => [
("profile" => "full"),
("subsystem" => "infinispan"),
("cache-container" => "*"),
("invalidation-cache" => "*"),
("component" => "eviction")
],
"outcome" => "success",
[...]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)