[
https://issues.apache.org/jira/browse/AMQ-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15042202#comment-15042202
]
Christopher L. Shannon commented on AMQ-6073:
---------------------------------------------
Thanks for pointing this out. I had tested this with our integration tests
which uses Jetty's client websocket client library and Firefox, and of course
that's the one browser that works :)
The issue is that most likely you are using the stomp.js library and that
library is setting the accepted sub protocol (the Sec-WebSocket-Protocol
header) as "v10.stomp" and "v11.stomp". However, the web socket server in
ActiveMQ is setting the accepted protocol to just plain "stomp", so there is no
match. I will put a fix in for this so in 5.13.1 all 3 protocol strings will
be there.
For now, as a work around, you should be able to specify the protocol if you
are using stomp.js (or any other websocket client). For stomp.js, if you look
at http://jmesnil.net/stomp-websocket/doc/ there is information on how to
change the subprotocol, which should be "stomp" for now. For example, you
would switch your connection line from:
{{Stomp.client(url)}} to {{Stomp.client(url, \['stomp'])}}
and that should work.
> WebSockets no longer working on most browers
> --------------------------------------------
>
> Key: AMQ-6073
> URL: https://issues.apache.org/jira/browse/AMQ-6073
> Project: ActiveMQ
> Issue Type: Bug
> Components: stomp
> Affects Versions: 5.13.0
> Environment: Mac OS X and Windows
> Reporter: Arnaud Marchand
> Assignee: Christopher L. Shannon
>
> It is no longer possible to open a web socket from the recent browsers such
> as : chrome, IE 11 and safari. Firefox is still working.
> It triggers an exception telling that the following header is missing:
> Sec-WebSocket-Protocol
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
