Create non-blocking socket with WiFiClientSecure #3872
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
SSL_READ_BLOCKING was causing the code to get stuck on functions using SSL socket (available(), connected() etc.) when connection to the server suddenly broke. As this was not really a stuck CPU WDT never fired.
|
I am having the same problem with wificlientsecure with the latest library. I Will try this solution. |
|
It is a good work around. |
|
Gonna close this due to axtls being deprecated now. If there is a similar issue w/BearSSL, please open a new issue and we can look at ways to make it happen. Thx! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SSL_READ_BLOCKING was causing the code to get stuck on functions using
SSL socket (available(), connected() etc.) when connection to the server
suddenly broke (in a manner that ESP still was associated to the AP and had an IP).
As this was not really a stuck CPU WDT never fired.