SecureDataSource

So I guess the data source object supports only supported HTTP and HTTPS not?  This seems rather incomplete for me. Not sure why BB would choose of does not support HTTPS.

In any case... someone at - he expanded the DataSource object to create a custom object of "SecureDataSource" or sorts. As far as I know, it's the only way to maintain the abstraction of the data source and have the ability to access secure servers?

any help is appreciated.  laucned an app... Cannot add... awesome https servers.

Ive been constantly changing things... and believe it or not... I just fixed that on my side.

Actually, I didn't need to use the signal at all. Of course it is better to deal with these issues. I was however able to get away with the not in need.

In the end I just need this.

    QSslConfiguration config = request.sslConfiguration();
    config.setPeerVerifyMode(QSslSocket::VerifyNone);
    // config.setProtocol(QSsl::TlsV1);
    config.setProtocol(QSsl::SslV3);
    request.setSslConfiguration(config);

Until the request is passed to the QNetworkAccessManager. I put audit peer votes to zero and SslV3 Protocol. This solved my problem of self-signed. I loaded the url in the blackberry browser and noticed that the certificate uses SslV3... not TlsV1. That is my question.

Going back to the good signal... all my google searches gave almost the same result... the sslErrors of the signal may or may not fire. Errors in the signal lights always... but even in this case, the ignoreSslErrors() method has nothing. Im guessing in the end, because of the Protocol, the handshake was not successful even so ignorant... has failed.

Tags: BlackBerry Developers

Similar Questions

Maybe you are looking for