i am, i find that the current interface is very sluggish (it even blocks the event loop(!)) with many users/vhosts and/or connections/channels. figured i could at least give it a try..
<br/><br/><br/><br/>On Monday 25 March 2013 at 22:55, Simon MacMullen-2 [via RabbitMQ] wrote:
<br/><div class='shrinkable-quote'><br/>> On 25/03/13 14:24, carlhoerberg wrote:
<br/>> > What about adding CORS headers to the mgmt HTTP API responses, so that the
<br/>> > API can be used from other client side apps?
<br/>> >
<br/>> > <a href="https://github.com/rabbitmq/rabbitmq-management/issues/3" target="_top" rel="nofollow" link="external">https://github.com/rabbitmq/rabbitmq-management/issues/3</a><br/>>
<br/>> As I said at the issue: we don't want to add
<br/>> "Access-Control-Allow-Origin: *", this is a security thing.
<br/>>
<br/>> Allowing you to configure mgmt so that it allows custom headers to be
<br/>> set would be OK I guess.
<br/>>
<br/>> What is your use case though? Are you intending to write an alternate
<br/>> web UI? :-)
<br/>>
<br/>> Cheers, Simon
<br/>>
<br/>> --
<br/>> Simon MacMullen
<br/>> RabbitMQ, VMware
<br/>> _______________________________________________
<br/>> rabbitmq-discuss mailing list
<br/>> [hidden email] (/user/SendEmail.jtp?type=node&node=25696&i=0)
<br/>> <a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_top" rel="nofollow" link="external">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br/>>
<br/>>
<br/>> If you reply to this email, your message will be added to the discussion below: <a href="http://rabbitmq.1065348.n5.nabble.com/CORS-in-the-mgmt-http-api-tp25693p25696.html" target="_top" rel="nofollow" link="external">http://rabbitmq.1065348.n5.nabble.com/CORS-in-the-mgmt-http-api-tp25693p25696.html</a>
<br/>> To unsubscribe from CORS in the mgmt http api, click here (<a href="" target="_top" rel="nofollow" link="external">
<br/>> NAML (<a href="http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml" target="_top" rel="nofollow" link="external">http://rabbitmq.1065348.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml</a>)
</div><br/><br/><br/>
<br/><hr align="left" width="300" />
View this message in context: <a href="http://rabbitmq.1065348.n5.nabble.com/CORS-in-the-mgmt-http-api-tp25693p25697.html">Re: CORS in the mgmt http api</a><br/>
Sent from the <a href="http://rabbitmq.1065348.n5.nabble.com/">RabbitMQ mailing list archive</a> at Nabble.com.<br/>