cancel
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

Anonymous
Not applicable

Hi,

Using wiced_https_get()

Whenever we try to communicate with our server (also tried other server) with a POST we always get response "after" 5 seconds. After a bit of investigation we found out that on the last packet reception it will always timeout (currently 5 seconds, see below code). However, the operation is still successful as we did able to get all the returned content from our server with POST. The main issue is the time as it always timeout on last packet reception. Help will be appreciated. thanks

This is the code of source problem in wicked_https_get() under http.c

rx_result = wiced_tcp_receive( &socket, &reply_packet, 5000 );

PS. Calling the same function wicked_https_get() with GET works fine. No response time issue as we saw with POST

Best Regards,

Aaron

0 Likes
Reply
1 Solution
Anonymous
Not applicable

My guess is that for a POST the server doesn't terminate the connection immediately leading to the timeout condition while a GET request, once served, is terminated leading to an immediate return from wiced_tcp_receive() rather than a timeout.

A sniffer trace should verify this.

The other option is to improve the extremely simple wiced_https_get() function to extract out length information and avoid doing the last call to wiced_tcp_receive().

View solution in original post

1 Reply
Anonymous
Not applicable

My guess is that for a POST the server doesn't terminate the connection immediately leading to the timeout condition while a GET request, once served, is terminated leading to an immediate return from wiced_tcp_receive() rather than a timeout.

A sniffer trace should verify this.

The other option is to improve the extremely simple wiced_https_get() function to extract out length information and avoid doing the last call to wiced_tcp_receive().

View solution in original post