SockJS和Webstomp的协议兼容性问题

Question

我正在使用Spring Boot和Angular构建网络聊天。为此，我将Websockets与客户端SockJS和Webstomp以及服务器端Spring一起使用。

问题是我在运行时在控制台上收到此错误：

已弃用：未定义不是公认的STOMP版本。在下一个主要客户端版本中，这将关闭连接。

我在google上进行了检查，并在github stomp项目上找出了该线程：https://github.com/JSteunou/webstomp-client/issues/75

这是与SockJS和Webstomp的协议兼容性的问题。

所以，我在以下代码中添加了options参数（即使over方法不允许使用协议参数？）

    var socket = new SockJS("http://localhost:8086/ws");
    var options = {debug: false, protocols: webstomp.VERSIONS.supportedProtocols()};
    var stompClient = webstomp.over(socket, options);

错误消息消失了。但是在请求标头中，仍然没有标头Sec-Websocket-Procotol来定义使用哪种协议，我认为将来会出现问题。

如何使我的代码正常工作？

客户端（角度）

  connectWebSocketRoom() {
    var socket = new SockJS("http://localhost:8086/ws");
    var options = {debug: false, protocols: webstomp.VERSIONS.supportedProtocols()};
    var stompClient = webstomp.over(socket, options);
    // var stompClient2 = webstomp.client(socket, ['v10.stomp', 'v11.stomp', 'v12.stomp']);

    stompClient.connect({}, function(frame) {
      console.log("test disconnect");
      stompClient.disconnect();
    });
  }

服务器端（春季）

@Configuration
@EnableWebSocketMessageBroker
public class WebSocketConfig implements WebSocketMessageBrokerConfigurer {

    @Override
    public void registerStompEndpoints(StompEndpointRegistry registry) {
        registry.addEndpoint("/ws").setAllowedOrigins("*").withSockJS();  
    }

    @Override
    public void configureMessageBroker(MessageBrokerRegistry config) {
        config.setApplicationDestinationPrefixes("/rooms"); 
        config.enableSimpleBroker("/topic", "/queue"); 
    }
}

请求和响应的标题：

请求

Host: localhost:8086
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:69.0) Gecko/20100101 Firefox/69.0
Accept: */*
Accept-Language: fr,fr-FR;q=0.8,en-US;q=0.5,en;q=0.3
Accept-Encoding: gzip, deflate
Sec-WebSocket-Version: 13
Origin: http://localhost:4200
Sec-WebSocket-Extensions: permessage-deflate
Sec-WebSocket-Key: SjoHYGkjTrPsDan0XmfgNg==
Connection: keep-alive, Upgrade
Cookie: access_token=eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJwaWVycmhvIiwicm9sZXMiOlsiUk9MRV9BRE1JTiIsIldSSVRFX0FDQ0VTUyIsIkRFTEVURV9BQ0NFU1MiLCJSRUFEX0FDQ0VTUyJdLCJpYXQiOjE1NjgxMjg1NzUsImV4cCI6MTU2ODEyODg3NX0.a4BNKm9qLbpEZFeMaI9seXSICWys3Exrumk9WyOqp6A
Pragma: no-cache
Cache-Control: no-cache
Upgrade: websocket

响应

HTTP/1.1 101 
Vary: Origin
Vary: Access-Control-Request-Method
Vary: Access-Control-Request-Headers
Access-Control-Allow-Origin: http://localhost:4200
Access-Control-Allow-Credentials: true
Set-Cookie: access_token=eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJwaWVycmhvIiwicm9sZXMiOlsiUk9MRV9BRE1JTiIsIlJFQURfQUNDRVNTIiwiV1JJVEVfQUNDRVNTIiwiREVMRVRFX0FDQ0VTUyJdLCJpYXQiOjE1NjgxMjg1NzYsImV4cCI6MTU2ODEyODg3Nn0.lD9wrYkztqWnihIqJodr3EpjMcMfBVUmbhxetBaGX5A; Max-Age=86400; Expires=Wed, 11-Sep-2019 15:16:16 GMT; Path=/; HttpOnly
Set-Cookie: access_token=eyJhbGciOiJIUzI1NiJ9.eyJzdWIiOiJwaWVycmhvIiwicm9sZXMiOlsiUk9MRV9BRE1JTiIsIlJFQURfQUNDRVNTIiwiV1JJVEVfQUNDRVNTIiwiREVMRVRFX0FDQ0VTUyJdLCJpYXQiOjE1NjgxMjg1NzYsImV4cCI6MTU2ODEyODg3Nn0.lD9wrYkztqWnihIqJodr3EpjMcMfBVUmbhxetBaGX5A; Max-Age=86400; Expires=Wed, 11-Sep-2019 15:16:16 GMT; Path=/; HttpOnly
Upgrade: websocket
Connection: upgrade
Sec-WebSocket-Accept: 9fahUc0KPDJ8vAUF2In5zZCGQTM=
Sec-WebSocket-Extensions: permessage-deflate
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-Frame-Options: DENY
Date: Tue, 10 Sep 2019 15:16:15 GMT

控制台屏幕：

Answer 1

您解决了吗？在线程中建议的修复程序正在使用Sock.js，但已弃用。