发表新帖
发表新帖

How to use TLS in Play!Framework WebSockets (“wss://”)

后端 未结
关注
4 1588
走了就别回头了
走了就别回头了 2020-12-05 08:51

I cannot use wss:// in my simple WebSocket app created with Play!Framework 2.2. It echoes the message back. The endpoint is like this

def indexW
相关标签:
4条回答
  • 清歌不尽
    2020-12-05 09:03

    wss works fine with Play 2.6.

    Instead of hardcode the websocket url, you can get the url via routes:

    @import play.api.mvc.RequestHeader
@import controllers.routes
@()(implicit request: RequestHeader)
<!DOCTYPE html>
<html lang="en">
    <head>
        <title>...</title>
        <script>
                var wsUri = "@routes.MyController.indexWS2().webSocketURL(secure = true)";
                var webSocket = new WebSocket(wsUri);
        //...
        </script>
    </head>
    <body>
    ...
    </body>
</html>
    0 讨论(0)
  • 刺人心
    2020-12-05 09:07

    I really wanted to figure this out for you! But I didn't like the answer. It appears there's no Play support yet for SSL for websockets. Saw mention of it here and no sign of progress since: http://grokbase.com/t/gg/play-framework/12cd53wst9/2-1-https-and-wss-secure-websocket-clarifications-and-documentation

    However, there's hope! You can use nginx as a secure websocket (wss) endpoint, to forward to a internal play app with a insecure websocket endpoint:

    The page http://siriux.net/2013/06/nginx-and-websockets/ provided this explanation and sample proxy config for nginx:

    Goal: WSS SSL Endpoint: forwards wss|https://ws.example.com to ws|http://ws1.example.com:10080

    "The proxy is also an SSL endpoint for WSS and HTTPS connections. So the clients can use wss:// connections (e.g. from pages served via HTTPS) which work better with broken proxy servers, etc."

    server {
    listen       443;
    server_name  ws.example.com;

    ssl on;
    ssl_certificate ws.example.com.bundle.crt;
    ssl_certificate_key ws.example.com.key;
    ssl_session_timeout 5m;
    ssl_protocols  SSLv2 SSLv3 TLSv1;
    ssl_ciphers  HIGH:!aNULL:!MD5;
    ssl_prefer_server_ciphers   on;

    location / {

        # like above

    }
}

    Nginx is so lightweight and fun. Would not hesitate to go with this option.

    0 讨论(0)
  • 执笔经年
    2020-12-05 09:07

    Did you try enabling https support on the Play server? It looks like you're trying to connect to the http port using wss, that can never work, you need to enable https, and then change the URL not just to wss, but also to use the https port.

    To start a Play server with ssl turned on:

    activator run -Dhttps.port=9443

    Then connect to wss://localhost:9443/ws2.

    0 讨论(0)
  • 借酒劲吻你
    2020-12-05 09:13

    Another option is to use SockJS as the Websocket layer, SockJS implementation for Play2 can be found at https://github.com/fdimuccio/play2-sockjs

    When HTTPS is enabled an wss endpoind is created by SockJS over the HTTPS channel. Play2-sockjs also supports the Actor pattern as with native Play websockets.

    If you don't want to use SockJS in the clientside but rather force browser websocket implementation, you can use explicit websocket endpoint wss:////websocket

    0 讨论(0)
 看不清?
提交回复
热议问题