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
I ran into a problem, when I had a client fast refreshing the loading of the web-site hosted on an ESP:
The connection was opened and then the client closed the connection (due to the refresh). This was written into the log ("An receive error occured, FID="), but in the HTTPConnection::loop(), this was not checked, the request still was answered:
So i changed the line before the switch to:
if (!isError() && _clientState != CSTATE_CLOSED)
Which solved the crashes...
The text was updated successfully, but these errors were encountered:
@trlink I see you've got an active fork of this, can I help contribute? we seem to be in about the same place bug-finding wise. Your repo doesn't allow issues directly
Hey Andrew,Sure, I need to check how to enable it...--Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 16.01.24, 12:31 schrieb Andrew Bullock ***@***.***>:
@trlink I see you've got an active fork of this, can I help contribute? we seem to be in about the same place bug-finding wise. Your repo doesn't allow issues directly
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
Hi all,
I ran into a problem, when I had a client fast refreshing the loading of the web-site hosted on an ESP:
The connection was opened and then the client closed the connection (due to the refresh). This was written into the log ("An receive error occured, FID="), but in the HTTPConnection::loop(), this was not checked, the request still was answered:
So i changed the line before the switch to:
if (!isError() && _clientState != CSTATE_CLOSED)
Which solved the crashes...
The text was updated successfully, but these errors were encountered: