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
When the ESP sends a close notification for a socket, that socket may still have data in its buffer.
However, when reading, we check for the "close" state first. So you are unable to read the remaining data.
To my understanding it may also be the case that the ESP sends out a close notification, still holding data for that socket. So we may have the additional issue of reading data from a socket we know that is closed, but need to drain the ESP's socket buffer.
The text was updated successfully, but these errors were encountered:
When the ESP sends a close notification for a socket, that socket may still have data in its buffer.
However, when reading, we check for the "close" state first. So you are unable to read the remaining data.
To my understanding it may also be the case that the ESP sends out a close notification, still holding data for that socket. So we may have the additional issue of reading data from a socket we know that is closed, but need to drain the ESP's socket buffer.
The text was updated successfully, but these errors were encountered: