Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

OpenSSL Problems



  • Hi everyone!

    I'm facing issues while using QNetworkAccessManager for HTTPS requests. I tried with my server but also with some link on badssl, to try to handle SSL Errors.

    So this is my code:

    manager = new QNetworkAccessManager();
            manager->setProxy(QNetworkProxy::NoProxy);
    
            connect(manager,&QNetworkAccessManager::finished,this,&alfro::managerFinished);
    
            connect(manager,&QNetworkAccessManager::sslErrors,this,&alfro::ignorsa);
    
    
    
    
            
    
    
              QSslConfiguration cfg(QSslConfiguration::defaultConfiguration());
              cfg.setProtocol(QSsl::AnyProtocol);
    
              request.setSslConfiguration(cfg);
              request.setUrl(url);
    
              manager->get(request);
    

    Where "ignorsa" is my sslErrors slot handler and managerFinished is the slot handler when everything is ok.

    The only reply I can get is "QNetworkReply::SslHandshakeFailedError" and the errorString "SSL Handshake failed", from the slot managerFinished, so sslErrors signals is not emitted!

    But the Qt Doc says that when this happens the sslErrors should be emitted! And in my case it not! Never!

    I'm going crazy on this, because I thing this is something stupid and I can't figure out!

    I'm currently using Qt 5.12.6 LTS and updated few hours ago to OpenSSL 1.1.1b (Feb 2019).

    If I try to write in console the version used for the build and for the runtime it says:

    Support SSL:  true
    SSL version used for build:  "OpenSSL 1.1.1b  26 Feb 2019"
    SSL version used for run-time:  269488207
    

    Thank you for your help!


  • Lifetime Qt Champion

    Hi,

    What OS are you on ?



  • Hi @SGaist!

    I'm currently using Windows 7 Professional SP1 x64.

    Any hint?


  • Lifetime Qt Champion

    Where are your OpenSSL dlls stored ? Can they be found by the application ?


Log in to reply