Azure Sphere HTTP Client C Code Example?

Sean

There are some HTTP related projects under Microsoft Azure Sphere samples:

https://docs.microsoft.com/en-us/azure-sphere/resources/sample-links

https://github.com/Azure/azure-sphere-samples

-Peter

Man, you are helpful and quick!  I need to be building my deck today on my day off, but you keep feeding my brain distracting me.

-Sean

Was able to get the example HTTPS client code to work.

Had it hit www.google.com with success.

However, api.darksky.net and the Nest Thermostat API gave this error

Connected to firebase-apiserver17-tah01-iad01.dapi.production.nest.com (52.4.203.41) port 9553 (#0)
* successfully set certificate verify locations:
*   CAfile: /mnt/apps/011b3254-6b4e-4af1-bc81-22e7f677f4bf/certs/DigiCertGlobalRootCA.pem
  CApath: /etc/certs/
* ALPN, offering http/1.1
*  CA signer not available for verification
* Closing connection 0
curl_easy_perform (curl err=77, 'Problem with the SSL CA cert (path? access rights?)')

Looks like I need to read up on SSL certificates to sort this one out.  Looks like I have to find a way to generate a new .pem file that will be acceptable by the nest server, in the above case.  Things that make you say "hmmmm???"

See ya',

Sean

Did you update your app_manifest.json file with the URL of the website you are accessing?

ie.

Yes.  Have it in there.

Used google and it worked.  Tried IFTTT and Yahoo as well.  However, they redirect out of the domain which results in a different problem.  Putting in the IP addresses directly fixes that, but results in getting the same CA signer not available for verification error.

Looks like in 2015 someone had a similar issue on another platform and it was due to the certificate:

https://www.wolfssl.com/forums/topic702-solved-ca-signer-not-available-for-verification.html

My bets are that I need to change out this file:  DigiCertGlobalRootCA.pem

Just don't know where to get it.

When I pulled this off in Linux on a raspberry pi, I used a package titled OpenSSL.  It didn't have me do anything with a certificate in the code itself.  Perhaps it handled that on its own.

See ya',

Sean

Sean

Not sure why you are bumping into this. The most efficient way to get quick resolution on this is to:
a) Summarize the issue as succinctly as possible and
b) Post this to the Microsoft MSDN Azure Sphere forum,
...that way we can get Microsoft specialist resources in the loop to advise

Here's the link:
https://social.msdn.microsoft.com/Forums/en-US/home?forum=azuresphere

-Peter

Thanks!  I entered a ticket.

I found one post with a similar issue that was resolved, but it was not clear on how he resolved it.  So, there is light at the end of the tunnel.

After this, I hope to make it catch web socket hits on a port.  Once I got this, I'll have it fully IoT tricked out ready to be an Alexa EndPoint.

See ya',

Sean

Haven't heard back yet on the forum, but I found this article that talked about how to work around the certificate.

I added this line in the main where the curl is doing all its setopts:

res = curl_easy_setopt(curlHandle, CURLOPT_SSL_VERIFYPEER, false);

It allowed it to return the api.  I feel I'm somewhat circumventing security, but, hey, I'm just asking for the current weather.

-Sean

Sean

You seem pretty resourceful! Good to hear you have a workaround :-)

PS: Which Weather APIs are you calling? (AccuWeather / Weatherbit / OpenWeatherMap / Dark Sky, etc?)

-Peter

I’m using Dark sky.  It returns a Json string that has about everything I’d ever need.

Next, I need to see if Microsoft already has a parser I can leverage.

see ya,

Sean