Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
06-25-2012 01:57 PM
I am making an api call to a web service url: https://api.github.com/users/octocat
I am getting the following console error
"Error: SSL handshake failed status:" Error retrieving feed: "Error: SSL handshake failed status:"
The call goes something like this:
QString queryUri = "https://api.github.com/users/octocat"; QUrl url(queryUri); QNetworkRequest req(url);
Do you guys know how to resolve this error? How does C++/Cascades handle calls to web services with HTTPS? All I need is to get the data back.
06-27-2012 03:46 PM
Thank you for your reply. I encountered the error via my console log (on device). I am not authenticating the client or using certificated, but the api endpoint is based on https.... Just need to make a simple call.
I will defer this issue. Solving this may not be worth the effort, esp for a niche application.