[
https://issues.apache.org/jira/browse/QPID-7563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15718828#comment-15718828
]
Rob Godfrey commented on QPID-7563:
-----------------------------------
I've made changes to allow virtual host aliasing and the provision of virtual
host specific REST services. All the servlets which deal with structure in
some form (REST, apidocs, Structure, MetaData, Query and QueueReports) have
been updated so that if the request is determine to have come through on a URL
which is aliases to a specific vhost, then the results from the servlet will be
specific to the vhost, and paths will reflect a vhost root.
I've also added a boolean attribute to HttpPort: manageBrokerOnNoAliasMatch.
If true (which is the default) then if there is no matching virtual host alias
for the URL (including the case where there are no aliases) then the port will
provide the traditional broker scoped API.
Note that even when scoped to a virtual host, the servlet will still serve up
static content, including the management GUI. Obviously attempting to use this
will fail as the GUI does not understand the vhost-centric paths/structure.
> Implement Virtualhost centric REST interface
> --------------------------------------------
>
> Key: QPID-7563
> URL: https://issues.apache.org/jira/browse/QPID-7563
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: qpid-java-6.2
> Reporter: Keith Wall
> Fix For: qpid-java-6.2
>
>
> For use-cases where the Broker to hosts a shared service where different
> applications are assigned to be different virtual hosts the broker should
> offer the ability to manage these virtualhosts independently. It should
> behave as if it were a chrooted prison.
> AMQP Management already offers this ability. The HTTP management interface
> should change to offer the same thing.
> The REST API of a virtualhost will service the only virtualhost's subtree.
> The formation of the service urls will reflect this structure.
> {{/virtualhost}} will be analogous to {{/broker}} and will service the
> virtualhost root. {{/queue/}} will serve all the queues defined on the
> virtualhost, {{/queue/<queuename>}} will serve only the names queue.
> To offer the virtualhost service, the HTTPPort will be changed to support
> VirtualHostAliases. As with an AMQPPort, with a HostNameAlias, a HTTP port
> will be capable of presenting an interface for any virtualhost whose name
> matches the hostname of the incoming request. A new alias type will support
> a one to one mapping between port and virtualhost interface.
> The scope of the initial work will be the REST API. It would be acceptable
> to leave the other services (SASL, structure, metadata) for a future JIRA.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
