-
Notifications
You must be signed in to change notification settings - Fork 7.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request: HTTP client library to check the binary length read from stream matches the HTTP he (IDFGH-594) #3004
Comments
trombik
pushed a commit
to trombik/esp-idf
that referenced
this issue
Aug 9, 2019
…ed stream and compare it with the size mentioned in the header. While downloading OTA firmware, if their is a Origin Respnse Timeout or the binary is only partially downloaded, OTA failure is observed. Checking binary size can also be helpful for simple http client applications. Closes espressif#3004
espressif-bot
pushed a commit
that referenced
this issue
Jan 24, 2020
…ed stream and compare it with the size mentioned in the header. While downloading OTA firmware, if their is a Origin Respnse Timeout or the binary is only partially downloaded, OTA failure is observed. Checking binary size can also be helpful for simple http client applications. Closes #3004
espressif-bot
pushed a commit
that referenced
this issue
Mar 23, 2020
…ed stream and compare it with the size mentioned in the header. While downloading OTA firmware, if their is a Origin Respnse Timeout or the binary is only partially downloaded, OTA failure is observed. Checking binary size can also be helpful for simple http client applications. Closes #3004
jack0c
pushed a commit
that referenced
this issue
Jul 29, 2020
…ed stream and compare it with the size mentioned in the header. While downloading OTA firmware, if their is a Origin Respnse Timeout or the binary is only partially downloaded, OTA failure is observed. Checking binary size can also be helpful for simple http client applications. Closes #3004
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Problem Description
Downloading firmware OTA via SSL using server certificates from a Hosting Server is working but when there is an Origin Response Timeout or Origin Keep-alive Timeout, in the middle of reading a http stream, this leads to a partial download of the binary requested, in consequence OTA failure. Current HTTP client library doesn't check the binary length matches the HTTP header. This would be a desirable feature to prevent OTA to continue update and retry in case binary size doesn't match HTTP header.
Expected Behavior
HTTP client library that checks the binary length read from http stream matches the HTTP header.
Other items if possible
Advised to be requested in a new issue #231
The text was updated successfully, but these errors were encountered: