Closed tpalaz closed 3 years ago
Again thanks for your nice words about the library.
I've just retested the Async_ESP_FSWebServer_DRD and didn't find out any issue as mentioned. Even the files are loaded from SPIFFS/LittleFS, the response time is very quick.
I suggest you start from scratch, move ahead methodologically until starting experiencing problem, then find out why.
I'm afraid without the same code and settings environment (networks, hardware, routers, etc. ), no one can duplicate the issue and help you.
Remember to use the IP address instead of the mDNS name to avoid unreliability of the mDNS.
For example: using 192.168.2.186/edit instead of http://async-esp8266fs.local/edit
Hello! I would like to share a problem which I have been experiencing now for roughly a week. On my ESP8266, the AsyncWebServer is often responding at a rate which is extremely slow (25s - up to 3 minutes). The sketch being used is a modified example (specifically, the DRD-Esp8266 Webserver). Here is the relevant code for webserver setup:
When connecting to either "/" or "/all", sometimes the response is extremely quick (3ms) or incredibly slow / times out. Here are the request headers (they are the same for both pages, and do not change if the response is slow/fast)
Similarily, here is the respone:
The timing console shows that the initial connection hangs (anywhere from instant to 10+ seconds), and then the Waiting(TTFB) hangs for a long time too (10ms --- 5+ minutes).
This happens randomly, and there is no indication that it is caused by memory. The heap available when making requests is consistently at ~32872, and at lowest drops to about 2.9.
If the request does not got through, this is the error:
(failed)net::ERR_CONNECTION_TIMED_OUT
There are no files being served, nothing. Interestingly, the captive portal almost always works and is always pretty quick to respond. I'm really confused what could be causing this. Iv'e tested on 2 seperate ESP8266 and both share similar results. As always, I am loving the library.