ESP32 Forum

Hi,

I have some code which calls a few functions in this order:


In clientConfig I do not specify a timeout but I have had a look at the code in esp_http_client_init and in that case it should provide a default timeout value of 5000 milliseconds. When the code executes I would expect that calling esp_http_client_fetch_headers will therefore allow up to 5000 milliseconds for the headers to be received.
At least that is what I think it should do when I look at the source code for that function.

However: I have log files from the UART output that clearly show that the output from both the ESP_LOGI calls above occur within the same microsecond.

The really odd thing is that I have several units that consistently report "Reported image length: -1" while others do provide the correct image length value. If I put my own 2 second time delay before calling esp_http_client_fetch_headers it always works OK. It very much looks like the timeout value is ignored but why ?

Any ideas/suggestions much appreciated.

Hi again,

I really wanted/needed to know what is causing this so I did some experimenting.

Instead of not providing a timeout value myself, and therefore relying on the code used in esp_http_client_init to fill in the default value of 5000 milliseconds, now I do provide a timeout value of 2000 milliseconds myself.

Sure enough: now it works perfectly OK, Once it calls esp_http_client_fetch_headers there is a delay of a few tenths of a second before the correct Image length is reported, exactly the sort of behaviour you would expect to see.

Its almost as if the section of code below in function _set_config in file esp_http_client.c is never executed.

An obvious reason this may happen is that client->timeout_ms is not 0 but something like 1 but it should be 0 as client points to a local variable declared, and therefore set to all 0, in the function that calls esp_http_client_init to set up and configure a new HTTP client.

I think you should report this here: https://github.com/espressif/esp-idf/issues
And could be somehow related to: https://github.com/espressif/esp-idf/issues/2684