http://localhost:61614
allowedMethods
GET,PUT,HEAD,OPTIONS
allowedHeaders
*
cross-origin
/*
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-Websockets-and-CORS-tp4708985.html
Sent from the ActiveMQ - User ma
cross-origin
/*
--
View this message in context:
http://activemq.2283324.n4.nabble.com/STOMP-Websockets-and-CORS-tp4670067p4672528.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Hi,
yes by default web socket spec defines same-origin policy and it's enforced
by web server (Jetty in this case). I just found out that there's a filter
that can be used to avoid this
http://wiki.eclipse.org/Jetty/Feature/Cross_Origin_Filter
so maybe we can make it configurable.
Regards
--
De
Paddy, can you confirm CORS is indeed not allowed with the current
implementation?
I peeked at the code really quick and I don't see anything specific to same
origin policy configurations, but if you confirm it cannot be done
currently, then open a jira and we can get that in there.
On Fri, Aug 2
Hi -
I'm trying to connect to a broker that is in a different domain than
where my web app is originating from. Following is what I read from the
ActiveMQ documentation:
One thing worth noting is that web sockets (just as Ajax) implements the*same
origin policy*, so you can access only brokers
