You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are hosting our binaries using Azure Functions. Azure Functions will close connections after five minutes (see the Azure Functions documentation). With a buffer size of 256, we often experience a timeout. We can fix the issue by changing the size of the OTA buffer but currently the only way to do so is by forking and modifying the IDF.
I'd like to propose a change: instead of fixing the OTA buffer size, set the OTA buffer size to the same value as buffer_size in esp_http_client_config_t.
The text was updated successfully, but these errors were encountered:
The OTA buffer used in
esp_https_ota
is currently a fixed size:esp-idf/components/esp_https_ota/src/esp_https_ota.c
Line 22 in 44b97b7
We are hosting our binaries using Azure Functions. Azure Functions will close connections after five minutes (see the Azure Functions documentation). With a buffer size of 256, we often experience a timeout. We can fix the issue by changing the size of the OTA buffer but currently the only way to do so is by forking and modifying the IDF.
I'd like to propose a change: instead of fixing the OTA buffer size, set the OTA buffer size to the same value as
buffer_size
inesp_http_client_config_t
.The text was updated successfully, but these errors were encountered: