[
https://issues.apache.org/jira/browse/AMQ-6073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15045088#comment-15045088
]
ASF subversion and git services commented on AMQ-6073:
------------------------------------------------------
Commit 913f64476b66c452fa03cb4fb8c09d831825bca5 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=913f644 ]
https://issues.apache.org/jira/browse/AMQ-6073
WSServlet for websockets will attempt to detect the subprotocol
requested and respond with the appropriate one. Currently the protocols
loaded are what stomp.js use for stomp (v11.stomp and v12.stomp).
If a protocol can't be found then a default will be returned, either
"stomp" or "mqtt", which is the same behavior before this patch.
This will make it a bit easier to use stomp over websockets out of the
box as stomp.js will work by default.
> 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
> Fix For: 5.13.1, 5.14.0
>
>
> 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)
