CC3220SF: How to set timeout for HTTPClient_connect

Hi Lorenzo,

For HTTPClient_connect(), there is no way to alter the timeout of the underlying TCP socket connect() call. This is fixed at ~10 seconds. You could edit the HTTP client library code to make that TCP socket non-blocking, but it would still result in a delayed timeout error returned to your socket callback after the timeout expires.

For HTTPClient_sendRequest(), there is also no way to directly implement a timeout. HTTPClient_sendRequest() performs send() calls as needed, and adding a timeout to the send() calls is not possible. You can only specify timeouts for recv() calls, as send() calls shouldn't be blocking in your application for any appreciable amount of time anyway given that function simply passes the send buffer to the NWP to process. Like the TCP connect function, send() has a hardcoded timeout of sorts based on TCP retries. If the TCP packets sent are not acked back after a fixed number of retries then an error will be returned from send(). This behavior cannot be modified. If you are concerned with the HTTP requests taking too long to send data while trying to send a very large request, you can implement an application timeout based on a timer where you check the system time after every send() to see if you're taking too long. There is however no method to set this through an API, you will need to edit the HTTPClient_sendRequest() function in the library to implement this yourself.

Let me know if you need more clarification on these TCP timeouts or if you have further questions on using the HTTPClient library.

Regards,
Michael