Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-72300

Can not connect with secure websocket server from chrome application

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Not Evaluated
    • Resolution: Done
    • Affects Version/s: 5.12.0 RC
    • Fix Version/s: None
    • Component/s: WebSockets
    • Labels:
      None
    • Platform/s:
      macOS

      Description

      Hi Team, we have a product is using boost library to implement secure websocket server . Now we want to use QtWebsocket to implement secure websocket server for new version of product. But we got some errors with QtWebsocket.

      Currently, we use a self signed root ca to sign for a local certificate which we use for websocket server. you can see example in here .
      This way works very well in v1 of our product.

      But when we change to use QtWebsocket, client app can not connect with websocket server.
      Need to have an extra step for user before client app can connect with server.

      after this step client app can connect with server

      I also see some differences between boost library and Qt library.
      In the keychain:

      • use boost library: I don't see the certificate with name "localhost"
      • user Qt library: I always see the certificate with name "localhost. Even I deleted it, it will appears again.

        Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

            Assignee:
            kurt.pattyn Kurt Pattyn
            Reporter:
            nguoithichkhampha Cuong Trinh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Gerrit Reviews

                There are no open Gerrit changes