Yes, it makes sense since they need to be together.<div><br></div><div>Thanks for clarifying.</div><div><br></div><div>Regards,<br clear="all">---<br>Massimo Paladin<br><br>email: <a href="mailto:massimo.paladin@gmail.com" target="_blank">massimo.paladin@gmail.com</a><br>
website: <a href="http://www.mpaladin.com/" target="_blank">http://www.mpaladin.com</a><br>flickr's page: <a href="http://flickr.com/photos/massimop" target="_blank">http://flickr.com/photos/massimop</a><br>
<br><br><div class="gmail_quote">On Tue, Jul 12, 2011 at 5:15 PM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com">simon@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 12/07/11 16:11, Massimo Paladin wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Other question, since 2.5.0 it is possible to instance the mgmt, api<br>
and acl in different contexts.<br>
I tried to set the mgmt with ssl on a specific port and the api on<br>
another port without ssl.<br>
<br>
This does not work because mgmt uses the api part with relative urls<br>
and mgmt stays empty....<br>
<br>
Is there any way to do what I am looking for?<br>
</blockquote>
<br></div>
Not really. You should only move contexts relative to each other if they don't know anything about each other, like management vs jsonrpc. In the next release the three management contexts will be merged into one anyway.<div>
<div></div><div class="h5"><br>
<br>
Cheers, Simon<br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, VMware<br>
</div></div></blockquote></div><br></div>