makeJsonRequest, https & SNI (Server Name Indication).

Former Member over 9 years ago

Hi,

Could not find an answer to my current issue: I'm trying to make a JSON request to an https endpoint (Amazon Web Services CloudFront distribution) but it does not work from the watch.

An example request would work from a web browser, the simulator, but not the watch. To be even more specific, the request from the watch works if I make it over http instead of https. So:

- web browser: http & https
- simulator: http & https
- watch: http but NOT https

CloudFront distributions are by default only supporting clients that can SNI. So my question is, does the SDK support SNI?

Kyle.ConnectIQ over 9 years ago

This should work as far as I know. Are you using Windows, iOS, or Android?

Former Member over 9 years ago

Watch is connected via an Android phone.

For an https request I get a '-300' response code from makeJsonRequest and the request does not even reach the backend.

travis.vitek over 9 years ago

For an https request I get a '-300' response code from makeJsonRequest and the request does not even reach the backend.

FYI, -300 is NETWORK_REQUEST_TIMED_OUT.

Former Member over 9 years ago

Well. In that case the https call is timing out much much much more faster than the request/response time on the http endpoint. I mean, I get the -300 response code immediately.

I can share (PM?) the https endpoint with you if you want to give it a try. As said earlier, only https from the watch does not work. All other combinations do.

This is kind of the last bit I'd like to get working before I have the complete chain up & running and can write an how-to write a widget backed by a serverless service running on AWS ;-)

Kyle.ConnectIQ over 9 years ago

Well. In that case the https call is timing out much much much more faster than the request/response time on the http endpoint. I mean, I get the -300 response code immediately.

I can share (PM?) the https endpoint with you if you want to give it a try. As said earlier, only https from the watch does not work. All other combinations do.

This is kind of the last bit I'd like to get working before I have the complete chain up & running and can write an how-to write a widget backed by a serverless service running on AWS ;-)

If you'd like you can email it to [email][email protected][/email] and we can take a look at it.

Former Member over 9 years ago

Would you mind sending the project/endpoint information to [email][email protected][/email]? I just recently pulled the latest Android GCM code to look into another issue and I can at a minimum look to see if the request is being received and forwarded within GCM. If you could include GCM version and the device you're using (with firmware version) that would be helpful too. Hopefully I'll be able to dig something up.

Former Member over 9 years ago

Just sent an email with more details.