Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. QSslSocket and unresolved functions
Forum Updated to NodeBB v4.3 + New Features

QSslSocket and unresolved functions

Scheduled Pinned Locked Moved General and Desktop
3 Posts 2 Posters 7.0k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • A Offline
    A Offline
    AttilaPethe
    wrote on last edited by
    #1

    Hello, I started to play with <QNetworkAccessManager>, <QNetworkRequest>, <QNetworkReply> and <QSslError>.

    If I write the next (trimmed down) code:

    @QNetworkAccessManager *manager = new QNetworkAccessManager();
    QString requestString="https://...........";
    QNetworkRequest request;
    request.setUrl(QUrl(requestString));
    QNetworkReply *reply = manager->get(request);@

    I got a lot of error during run-time:

    QSslSocket: cannot call unresolved function SSLv23_client_method
    QSslSocket: cannot call unresolved function SSL_CTX_new
    QSslSocket: cannot call unresolved function SSL_library_init
    QSslSocket: cannot call unresolved function ERR_get_error

    I mention that I set up this code after the event dispatcher is running (at least I hope so) and I connected the finished(QNetworkReply*), readyRead(), error(QNetworkReply::NetworkError) and sslErrors(QList<QSslError>) signals to my own (empty, yet) slots.
    Where to search for the problem? My code segfaults too.
    I understood that maybe I have to install OpenSSL (Win32 OpenSSL or Win64 OpenSSL). What to install if I use W7PRO 64? What SSL package/version is recommended?
    Thanks!!!

    1 Reply Last reply
    0
    • C Offline
      C Offline
      ChrisW67
      wrote on last edited by
      #2

      You need the 32-bit version of OpenSSL.dll if your application is compiled 32-bit, and the 64-bit version if your application is compiled 64-bit. It makes no difference if your 32-bit application is running on a 64-bit machine. The DLL must be put somewhere it can be found for on-demand DLL loading by your application.

      1 Reply Last reply
      0
      • A Offline
        A Offline
        AttilaPethe
        wrote on last edited by
        #3

        Yes you are right! Uninstalling the 64 bit version and installing the 32 bit version solved the problem! Thanks for suggestion!

        1 Reply Last reply
        0

        • Login

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Users
        • Groups
        • Search
        • Get Qt Extensions
        • Unsolved