[jboss-jira] [JBoss JIRA] (WFLY-5012) Resource alias operation inconsistencies
Brian Stansberry (JIRA)
issues at jboss.org
Tue Aug 11 18:15:04 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13097471#comment-13097471 ]
Brian Stansberry commented on WFLY-5012:
----------------------------------------
I don't if we can do anything about this in the next few weeks, so if you can not use the alias that's better.
> 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: Brian Stansberry
> Priority: Blocker
> Fix For: 10.0.0.Beta2
>
>
> 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 at 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)
More information about the jboss-jira
mailing list