WiFiClientSecure gets stuck, when send buffers get full #2494
Description
When we send too fast (faster then the TLS connection allows), eventually the send buffers will fill up and write() returns 0 (indicating, that nothing could be written). Normally this means we just retry until all data is sent, but in this case the TLS socket never recovers from this condition (buffers stay full). The only thing we can do is close the socket and go home.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Participants
Activity
stale commentedon Aug 1, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
everslick commentedon Aug 1, 2019
still valid, don't close.
stale commentedon Aug 1, 2019
This stale issue has been automatically closed. Thank you for your contributions.
everslick commentedon Aug 1, 2019
esp8266/Arduino#6104
could be the same bug as on ESP8266. @me-no-dev ?
stale commentedon Sep 30, 2019
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
everslick commentedon Sep 30, 2019
still relevant, don't close.
stale commentedon Sep 30, 2019
[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future.
stale commentedon Nov 29, 2019
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.
everslick commentedon Nov 29, 2019
still relevant, don't close.
stale commentedon Nov 29, 2019
[STALE_CLR] This issue has been removed from the stale queue. Please ensure activity to keep it openin the future.
23 remaining items