-
Notifications
You must be signed in to change notification settings - Fork 7.3k
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
[TW#27054] esp_http_client issue - Wrong content length set #2638
Comments
You are right, the value is not used at all. It should do esp-idf/components/esp_http_client/esp_http_client.c Lines 1085 to 1095 in 3977d4b
|
Alvin1Zhang
changed the title
esp_http_client issue - Wrong content length set
[TW#27054] esp_http_client issue - Wrong content length set
Oct 29, 2018
igrr
pushed a commit
that referenced
this issue
Feb 28, 2019
Fixed with 2e3f06e, closing. |
catalinio
pushed a commit
to catalinio/pycom-esp-idf
that referenced
this issue
Jun 28, 2019
0xFEEDC0DE64
pushed a commit
to 0xFEEDC0DE64/esp-idf
that referenced
this issue
May 5, 2021
Currently WiFiClient::write is unable to send messages over 25Kb, because of the hard-coded retry limit of 10, that is getting decremented on every successful send. Since we cannot send more than 2*MTU bytes in one go, and have only 10 retries, write() is limited to approximately 25Kb. Technically it is not a bug, as it correctly returns the number of sent bytes and the caller can set up futher retries. But not all libs are aware of this behavior, for example, WebServer is not. I suggest improving current behavior by resetting retry counter every time we had a successful write, so the limit of 10 retries will apply to Failed writes only, and will not apply to Successful writes. This will allow to write() blobs of arbitrary sizes.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment
Problem Description
esp_http_client_open() API should set "Content-Length" header to the passed size. But the content-length header is either not set or it is set to 0.
I am trying to send a file from esp32 as attachment to a server. Here is the same code for the same.
Code to reproduce this issue
Debug Logs from server
The text was updated successfully, but these errors were encountered: