aagiannidis
commented
2 years ago Just before the arduino becomes non-responsive i can see from the logs that prepareHeader is executing but the send function is not executed.
16:54:55.123 -> [EWS] handleClient: New Client
16:54:55.157 -> [EWS] method: GET
16:54:55.157 -> [EWS] url: /login
16:54:55.157 -> [EWS] search:
16:54:55.157 -> [EWS] headerName: Host
16:54:55.157 -> [EWS] headerValue: 192.168.1.30
16:54:55.157 -> [EWS] headerName: Connection
16:54:55.157 -> [EWS] headerValue: keep-alive
16:54:55.157 -> [EWS] headerName: Cache-Control
16:54:55.157 -> [EWS] headerValue: max-age=0
16:54:55.190 -> [EWS] args:
16:54:55.190 -> [EWS] args count: 0
16:54:55.190 -> [EWS] args:
16:54:55.190 -> [EWS] args count: 0
16:54:55.190 -> [EWS] Request: /login
16:54:55.190 -> [EWS] Arguments:
16:54:55.190 -> [EWS] Final list of key/value pairs:
16:54:55.190 -> [EWS] _handleRequest handle
16:54:55.190 -> [EWS] send1: len = 162
16:54:55.190 -> [EWS] content = <html><body><form action='/login' method='POST'>To log in, please use : admin/password<br>User:<input type='text' name='USERNAME' placeholder='user name'><br><br
16:54:55.224 -> [EWS] _prepareHeader sendHeader Conn closeThis bit is missing from the log (taken from full ok example above)
22:08:19.554 -> [EWS] send1: write header =
22:08:19.554 ->
22:08:19.554 -> [EWS] sendContent: Client.write content: User:<input type='text' name='USERNAME' placeholder='user name'><br>
22:08:19.554 -> [EWS] _handleRequest OK
22:08:19.589 -> [EWS] handleClient: Don't keepCurrentClientI think the problem occurs in this function
void EthernetWebServer::send(int code, const char* content_type, const String& content)
{
String header;
// Can we asume the following?
//if(code == 200 && content.length() == 0 && _contentLength == CONTENT_LENGTH_NOT_SET)
// _contentLength = CONTENT_LENGTH_UNKNOWN;
ET_LOGDEBUG1(F("send1: len = "), content.length());
ET_LOGDEBUG1(F("content = "), content);
_prepareHeader(header, code, content_type, content.length());
_currentClient.write((const uint8_t *)header.c_str(), header.length());
if (content.length())
{
ET_LOGDEBUG1(F("send1: write header = "), header);
//sendContent(content);
sendContent(content, content.length());
}
}
khoih-prog
Dear all, first of all i need to congratulate you on this wonderful library. I dont want to waste anyones time but I am desperate to find a solution. I can see that this topic is somehow similar to a previous one but I am confident that it is a valid case to be examined.
I am using an arduino Mega with an ethernet shield 2. The device is powered from USB cable directly connected to laptop. I have developed my own program and came across some issues that I couldnt explain. Finally i went back to the drawing board and conducted my tests with the Simple Authentication example as provided. I could replicate the issues with this example so it makes me think there is a bug somewhere in the library.
The bug is as follows: after consecutive refreshes the arduino starts sending less and less data and finally i get the message connection refused on the browser. The arduino seems to be stuck as it produces nothing. However it responds to pings Ok.
Here is some info on how to replicate the bug:
Arduino 1.8.13 Arduino Mega plus Ethernet Shield 2 featuring a W5500. Example: Simple Authentication Page to refresh: $IP ADDRESS$/login Browser: Chrome and Firefox Configuration settings: using either Ethernet or Ethernet2 library
Load the page and do about 200 refreshes. Refreshes should be done once the page is loaded. On every refresh the arduino should send 350 characters with the content
<html><body><form action='/login' method='POST'>To log in, please use : admin/password<br>User:<input type='text' name='USERNAME' placeholder='user name'><br>Password:<input type='password' name='PASSWORD' placeholder='password'><br><input type='submit' name='SUBMIT' value='Submit'></form><br>You also can go <a href='/inline'>here</a></body></html>After 150-200 refreshes the arduino starts sending less and less characters. Please see provided log further down.
Also, if the refreshes are faster the arduino will also report corrupted data on its parsed received headers. Please see provided log further down.
Here is a perfect page refresh log that sends the full 350 character long web page:
After 150-200 refreshes it sends less data. In this case it sends 237 characters only.
After a few more refreshes it sends 90 characters
And eventually you get the ERR_CONNECTION_REFUSED from the browser. The arduino at this point seems to be stuck as it does not produce and logs but weirdly it responds to pings Ok.
Finally, when someone goes crazy with the page refresh and keeps refreshing very fast, i can see corrupted data on the headers too...See below (please note how the ip address is not correctly filled in):
and also some funny log that shows things really messed up