-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only the first ~2.5KByte is served for static files #63
Comments
I am serving quite large files here, so things should be fine. Your log shows that it can not find many files. Are you sure you have all files there and that your SPIFFS is ok? I have it tested with 2MB files up and down ;) |
Thanks for your fast response. I am happy to hear that ESPAsyncWebServer is capable of handling even very large files. Then the problem must be in my setup. In order to rule out SPIFFS problems, I will add a second regular synchronous webserver to port 81 to see if it the download is ok with that. I will come back with the results. |
I've investigated further. And it looks the issue is related to my wifi network at home. (I have two AP-s one of them is running OpenWrt and that is linked via wifi to another AP, when I've removed the openwrt AP then it started to work fine) |
I have the same problem on a WIFI network based on multiple Ubiquiti UniFi AP-LR. It works with no problems on a Asus wifi router. Maybe someone sees this and knows a possble answer to this problem. |
I have the same problem. It does not work with Cisco 3602 AP's but works with iPhone as client. |
Enable Github CI
Hi me-no-dev,
I have uploaded the ESP_AsyncFSBrowser to my nodemcu but it looks like it struggles sending large files.
I have tried it with many different client (IE, firefox, chrome) but it's the same. The same SPIFFS content seems to work the default arduino webserver, but it's terribly slow. I have tried both gzipped and non gzipped version of the file but it's the same.
I am using the master/head for both the ESPAsyncWebserver and ESPAsyncTCP.
The text was updated successfully, but these errors were encountered: